CICA 1994 April/CICA Shareware for Windows CD-ROM (Walnut Creek CD-ROM)(April 1994).ISO/win3/access/access_l.exe/ACC9305.TXT

Text File | 1994-01-07 | 225KB | 5,131 lines

=========================================================================
Date:         Sat, 1 May 1993 13:04:40 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Brian Henning <[e-mail]>
Subject:      How to create a running line counter for a report

Hi,

I'm developing a report that will represent an invoice.  The  invoice has
summary info and then detail lines representing  the items on the order.  I
would like to have a running line  item count in the first column of the detail
lines.

... Customer info ...

Line    Item     Description...
1       abc      ...
2       def      ...
3       xyz      ...

I can't figure out how to create a running count for that  first column via the
underlying query or the report itself.   I've tried playing around with running
sums and counts to no  avail. This seems like such a straight forward
requirement  of a report writer where you want to label things 1 to n..

Thanks.

Brian Henning
[e-mail]
=========================================================================
Date:         Sun, 2 May 1993 14:30:01 +0100
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Martin Brynskov <[e-mail]>
Subject:      How to use subqueries (ANSI SQL feature not implemented in ACCESS)

Dear fellow Access users,

we all like this new RDBMS - or at least we are now trying to figure out
the pros and cons of the way it's done.

I have yet to discover how to implement the following ANSI SQL statement in
an Access database:

I have 3 tables (A, B, C) where B is the joining table containing A_ID and
C_ID.

I would like to

SELECT A_ID FROM A
WHERE NOT EXISTS (SELECT A_ID FROM B
                  WHERE C_ID = "Joe");

I can't see where to put the NOT. It's easy enough to nest queries
(suggested in the manual to substitute subqueries) without the NOT operator
in between.

Do any of you see my problem - is it simple..?

I would appreciate even the slightest hint where to look for the proper way
to do this in Access. Please reply via e-mail.

TIA,
Martin.
________________________________________________________
Martin Brynskov
[e-mail]
Aarhus, Denmark
=========================================================================
Date:         Mon, 3 May 1993 10:44:15 +1000
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         margaret eva <[e-mail]>
Subject:      form view from tables

Forgive me if I am being dense.  I am accustomed to a flat file data base
(PC-FILE) in which it is very easy to select a record while browsing (=
table view in Access) and display that record in form view (only way to
see the whole record at once).  I can't find anything in the manual.  It
seems such an obvious thing to do that I must have missed something?

advice will be gratefully received
Margaret Eva
University of Queensland
=========================================================================
Date:         Mon, 3 May 1993 08:20:34 +0100
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     Warning -- original Sender: tag was [e-mail]
From:         Stefan Focke <[e-mail]>
Subject:      Re: form view from tables

In Message Mon, 3 May 1993 10:44:15 +1000,
  margaret eva <[e-mail]> writes:

>
>Forgive me if I am being dense.  I am accustomed to a flat file data base
>(PC-FILE) in which it is very easy to select a record while browsing (=
>table view in Access) and display that record in form view (only way to
>see the whole record at once).  I can't find anything in the manual.  It
>seems such an obvious thing to do that I must have missed something?

Select one record and press the form-button in the toolbar.

Stefan

----------------------------------------------------------------------

Stefan Focke                  Tel. [phone]
GMD-ISA                       e-mail: [e-mail]
Rathausalle 10
D-W 5205 Sankt Augustin 1

    ********** MS-Word: From the guys who brought us EDLIN ********
=========================================================================
Date:         Mon, 3 May 1993 14:01:14 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Diamond SpeedStar PRO

Hi to all!

Since I use a Diamond SpeedStar PRO I encounter quite frequent system
crashes of the annoying kind: most of the time I get GPFs in one of the
Access DLLs but also in MSACCESS.EXE amd sometimes in KRNL386.EXE which
causes my machine to boot or at least to lose the Progman.

I any of these cases I choose to at least start Windows again.

The visible speed and of course the benchmarks are great for this quite
cheap card.

Any hint appreciated (new drivers for this card?)

Martin
=========================================================================
Date:         Mon, 3 May 1993 15:35:00 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Out of memory

Hi again!

I'm getting "out of memory"-messages when opening reports.

Is there any other hint than to increase files= in config.sys???

I have about 20 dBase-files and about 20 queries with not more than 20 - 40
fields.

Any help appreciated

Martin
=========================================================================
Date:         Mon, 3 May 1993 06:59:44 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         John von Colditz <[e-mail]>
Subject:      Re: Diamond SpeedStar PRO
In-Reply-To:  <[e-mail]> from "Hilger Martin Dr." at
              May 3, 93 02:01:14 pm

>
> Hi to all!
>
> Since I use a Diamond SpeedStar PRO I encounter quite frequent system
> crashes of the annoying kind: most of the time I get GPFs in one of the
> Access DLLs but also in MSACCESS.EXE amd sometimes in KRNL386.EXE which
> causes my machine to boot or at least to lose the Progman.
>
> I any of these cases I choose to at least start Windows again.
>
> The visible speed and of course the benchmarks are great for this quite
> cheap card.
>
> Any hint appreciated (new drivers for this card?)
>

I have used the SpeedStar Pro board, and experienced similar problems.
I now have a Viper.  In the course of downloading new drivers for my
Viper, I noticed new drivers for the SpeedStar Pro, dated April 28 or
so.  These may solve your problems.  (They are on CompuServe's Diamond
Forum, and probably on their BBS).  In the interim, do the following to
minimize GPF's.
     - Save whenever you edit any object in Access.  Save immediatly
       after the changes are made.
     - Whenever you get a GPF do a _hard_ reset.  Even a Ctrl-Alt-Del
       will not reset the board.
This should keep the rate of GPF's under 1/30 minutes until you get the
new drivers.

John

> Martin
>
=========================================================================
Date:         Mon, 3 May 1993 16:29:51 +0200
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Ofer Sheinkin, Sheinkin Consulting Ltd.,
              SubContractor to DEC 03-May-1993 1731" <[e-mail]>
Subject:      unsubscribe

please unsubscribe me
=========================================================================
Date:         Mon, 3 May 1993 23:22:39 -0700
Reply-To:     Kristina Sontag <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Kristina Sontag <[e-mail]>
Subject:      Re: form view from tables
In-Reply-To:  <[e-mail]>

On Mon, 3 May 1993, margaret eva wrote:

> Forgive me if I am being dense.  I am accustomed to a flat file data base
> (PC-FILE) in which it is very easy to select a record while browsing (=
> table view in Access) and display that record in form view (only way to
> see the whole record at once).  I can't find anything in the manual.  It
> seems such an obvious thing to do that I must have missed something?
(more cut...)

You will need to be in form view, not table view to do this and your form
must have the views allowed property set to both (allows you to view data
either in form or datasheet view). Use the datasheet button on the menu
bar to browse through the records, then choose the form view button
to view the record in the form once you have it selected.

Hope this helps!

--kris

Kristina Sontag
[e-mail]
=========================================================================
Date:         Tue, 4 May 1993 10:51:48 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Page 1 of XX Pages???

Hi to all!

Is there a way to put "Page 1 of XX Pages" in a report? I couldn't find
any.

Any hint appreciated!

Regards

Martin
=========================================================================
Date:         Tue, 4 May 1993 13:33:45 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Amy Park <[e-mail]>
Subject:      Page Numbering

I foolishly discarded Martin Hilger's question before responding to it, but
he wanted to know about numbering pages with "Page # of 5."

Go into the Design mode in your report, and add a text box to the Page Footer
section.  Enter the following in the box:

       ="Page " & Page & " of 5"

or whatever you want it to say.

Hope it works for you!


Amy Park ([e-mail])
=========================================================================
Date:         Tue, 4 May 1993 13:38:09 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Access Performance

I am in the process of developing(99% done) a database to track the
location and specifications of computer hardware on our campus.  I have
over 4300 records in the database and I'm running on a 66Mhz DX2.  The
performance in Access is pretty zippy.

I've run the same data base on a 386 16Mhz IBM PS/2 Mod 55 and found the
performance a little less that desired. I'm wondering what expirences any
of you might be having running large data bases on various CPU classes and
clock speeds?

Has anyone herd when the run-time module for Access will be released?

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
_________________________________________
=========================================================================
Date:         Tue, 4 May 1993 15:44:48 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Access Performance
In-Reply-To:  Message of Tue, 4 May 1993 13:38:09 -0700 from <STEWART@GC>

I'm running it on two different machines.

Primary Machine:  PS/2 Model 56SLC, 20mhz 386SLC, 6MB RAM.  Access runs
                  "acceptably" but could stand to be a little faster.
                  Takes too long to pull up forms for either preview
                  or design, but beats the tar out of dBase for ease
                  of operation.  I'll give it an 8 on this machine.

Secondary Machine:  Generic 386DX-33 cache motherboard with 4MB RAM.
                  Put succinctly, performance sucks.  I am aware that
                  I need more RAM, so I don't complain much.  :)  It's
                  usable, but only just, in this environment.  I might
                  add that this machine is still running 8-bit cards
                  because I ain't got the money to upgrade 'em--that
                  contributes to the generally-lobotomized operation.
                  I'll give it a 6 and say it still beats the tar out
                  of dBase.

BTW, both machines are running DOS 6 and have been optimized with
MemMaker.  (What a neat little program!)  And I did bite the bullet
and gave my hard drive over to the tender mercies of DoubleSpace...
which doesn't do as good a job as Stacker, but at least it doesn't
crash my system.  :)

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Tue, 4 May 1993 17:52:19 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Remailed message/WAS:  Re:Access Performance

Here's another error that didn't have to happen...Please, please,<please>
remove header junk that doesn't need to go with your replies...PLEASE!

[Forwarded Message Begins]

The  enclosed mail  file, found  in the  ACCESS-L reader  and shown  under the
spoolid 8411  in the console log,  has been identified as  a possible delivery
error notice for the following reason: "Sender:", "From:" or "Reply-To:" field
pointing to the list has been found in mail body.

[Much extraneous header junk removed]

>Date: 04 May 1993 14:01:28 -0700 (MST)
>From: "MICHAEL G. MAITLEN" <[e-mail]>
>Subject: Re: Access Performance

[Much more extraneous header junk removed]

I am in the process of developing(99% done) a database to track the
location and specifications of computer hardware on our campus.  I have
over 4300 records in the database and I'm running on a 66Mhz DX2.  The
performance in Access is pretty zippy.

I've run the same data base on a 386 16Mhz IBM PS/2 Mod 55 and found the
performance a little less that desired. I'm wondering what expirences any
of you might be having running large data bases on various CPU classes and
clock speeds?

Has anyone herd when the run-time module for Access will be released?

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
_________________________________________

     I  run  Access  on both a 386 SX25 and a 486 DX50.  The performance on
the 386 is well below  that  of  the  486.  I was able to speed up the 486,
which  is  handling a database of about 30,000  records,  by  changing  the
WIN.INI file,  but  this  was  only  because  the  486 is running on 8 megs
whereas the 386 has only 4.

     I was wondering if there is anyway to speed up  the query process.  It
works great when I transfer the database on the 386, about 4000 records, to
the  486, but when I work on the larger database it runs  like  a  dog.   I
could  just  be maxing out the software though.  Not only do I have 30,000+
records, but due  to  the  complexity  of  the  accounts, each has about 30
fields.

     Also, the oldtimers in the company I intern  for insist on using Alpha
Four for networking the database rather then Access.   Does  anyone  have a
reply  to  that,  I still fairly new to databases, and know even less about
networks.  I feel much  more  comfortable with Access, but Alpha Four has a
longer history.  I hate thinking  about  having to use an attached table to
output our reports, and use the gui interface  for  the  salesmen  who know
nothing  about computers.  I'm using an attached table for the database  on
the  386, and it makes everything go at snells pace.

     Thanks for your comments

Michael G. Maitlen
Arizona State University
Tempe, Arizona

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Tue, 4 May 1993 16:39:22 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Actions can get executed before the conditional expressions

I found a rather annoying bug (feature?) today with Access and macros.
I have a macro that calls a function as part of the conditional expression.
If the expression is true, I expect access to execute the action and any
further actions that have the elipsis (...) in the conditional column.

To my amazement, I see that the Action gets executed before the conditional
expression is executed! After much debugging (and frustration, since the
Action was to delete some records), I found that if you define an Action
that executes "RunCode" and specifies the function with =FunctionName(), this
improper behavior occurs. If you specifiy the function name (operand of
the RunCode action) without the preceding '=' (equal sign), then everything
works as expected.

To reiterate, when using the RunCode action in a macro, make sure to leave
off the '=' from the front of the function name. I had this coded for a long
time now and it worked ok. But, I recently put a condition in front of this
RunCode action and Access executes the Action before checking the condition.
I verified this by putting traps in the conditional code and the action code.

Later,


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Tue, 4 May 1993 18:25:50 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: Access Performance

I've noticed that Access works best with 8MB's or more RAM.  I guess for
some reason it just performs a little faster.  I think it has to do with
having all of the SIMM slots on the motherboard filled, therby eliminating
any wait-states.

I'm glad to hear that Access runs decent on the PS/2.  We're running
OS2/2.0 on the same equipment and it's a real sloth.

Bill
=========================================================================
Date:         Tue, 4 May 1993 17:08:34 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Access Listserv <[e-mail]>
Subject:      Re: Access Performance
In-Reply-To:  <[e-mail]>

On Tue, 4 May 1993, Bill Stewart wrote:

> I am in the process of developing(99% done) a database to track the
> location and specifications of computer hardware on our campus.  I have
> over 4300 records in the database and I'm running on a 66Mhz DX2.  The
> performance in Access is pretty zippy.
>
> I've run the same data base on a 386 16Mhz IBM PS/2 Mod 55 and found the
> performance a little less that desired. I'm wondering what expirences any
> of you might be having running large data bases on various CPU classes and
> clock speeds?

Application:

        Database conversion from fixed width files of 750k and 1750k in length
into three related tables with up to 3500 records, various calculations
and string manipulations being done to the data as it's imported (~20
pages of code used in the conversion).

System 1:
386?X/25 Laptop with 4 MB RAM
Performance acceptable, ~1.5 hours to do the conversion

System 2:
486SX/25 Desktop with 4 MB RAM
Performance acceptable, ~1 hour to do the conversion
With buffer enlarged from 512k to 1024k or 2048k, performance miserable,
killed the process before it was done -- I could watch the records be
updated at 1-5 seconds per record!

System 3:
486DX/25 Desktop with 8 MB RAM
Performance Excellent, ~15 minutes to do the conversion
No visible change with enlarged buffer to 1024k, 2048k, or 4096k.
Visible slowdowns when other large programs like Excel or Word are running.

486DX/25 with 13 MB RAM
No visible performance difference from above (except for the other
programs running.)

Conclusion?  Access is highly sensitive to amount of RAM present, less so
to processor speed.  8 MB RAM is plenty for small data sets, 4 mb RAM can
handle only the smallest amounts of data before it croaks (my 500 record
tables sort ok, 3000 is much slower).  Upgrading past 8 MB isn't needed
unless you don't want to be concerned with what other applications you're
running or unless you're running a lot more data than I am.

 - jcb
=========================================================================
Date:         Wed, 5 May 1993 02:20:01 +1000
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         /R=ECC/R=AM/U=IT_GREG/FFN=IT_GREG/@MR.TASED.EDU.AU
Subject:      Re: Access Performance
In-Reply-To:  <01GXTE0P2WRO95MP2S*@mr.tased.edu.au>

I have been developing a system to pay student accomodation
allowances, which required a lookup table for the Bank code.

The table contained 13000 records and took almost a minute to find a
specific (and indexed) record. I talked to the Microsoft help desk and I
was doing all the right things.

This performance is really poor. The help desk suggested that FOXPRO
might be more appropriate. (The machine was a 486sx 25)

Greg Curtis
Snr Systems Officer
Dept Education and the Arts
Tasmania
Australia
=========================================================================
Date:         Tue, 4 May 1993 22:40:46 -0500
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         George Raudabaugh <[e-mail]>
Subject:      Re: Access Performance

Per some contact with folks at MS (very anon):

You want to build small stuff/use Access.

You want it to fly/use Fox.

Unfortunate, in that Access was cheap and really is easy to build apps with.
Maybe the fabled ODBC links will speed it up (if you have the underlying
DBMS).  However, I don't expect Access Vx.x to ever approach Fox speed
unless the products are merged (and I think the $90 price tag will go
bye-bye if this happens).   I see Access more as a developement tool, not
really a DBMS (competing with JYACC Jam/IBI Focus/Uniface IDF).

This is mostly opinion, so take it with a grain of salt.

GR.
--
George Raudabaugh               Manager/Document Technologies
Information Dimensions, Inc.    [e-mail] (work email)
5080 Tuttle Crossing Blvd.
Dublin, Ohio  43017             [phone]                     (voice mail)
=========================================================================
Date:         Tue, 4 May 1993 21:24:54 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Dan Tauber <[e-mail]>
Subject:      Re: Access Performance
In-Reply-To:  <no.id>; from "George Raudabaugh" at May 4, 93 10:40 pm

I just saw Bill Gates talk at DB Expo in San Francisco and basically he said

* Access is designed to make building apps easy. The goal was to make it easy
for users to get to the data.
* If you want to do real database stuff with Access (large datasets/fast
transaction times) you need to have a database backend such as SQL Server
for NT or Sybase.
* FoxPro is real fast and MS plans on putting the Fox database engine into
other products.

Dan Tauber
[e-mail]
=========================================================================
Date:         Tue, 4 May 1993 21:28:45 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Dan Tauber <[e-mail]>
Subject:      Parsing E-Mail with Access
In-Reply-To:  <no.id>; from "George Raudabaugh" at May 4, 93 10:40 pm

Has anyone written some Access code to parse e-mail into a
database? What I want to do is read in a text file that contains
lots of messages. Pull out a number of fields, from, to, subject,
etc. and then put the entire text of the message into a memo field.

I have a few personal applications for this and if it works I also
have a use for it at work.

Dan Tauber
[e-mail]
=========================================================================
Date:         Wed, 5 May 1993 15:38:44 -0500
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Robert Boot <[e-mail]>
Subject:      Re: Parsing E-Mail with Access

If you hear anything on this I should also be very interested.

Robert Boot
Herston Medical Library
University of Queenslandd
Australia

[e-mail]
Ph: [phone]
=========================================================================
Date:         Wed, 5 May 1993 08:08:32 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Pekka Koskinen CIMO <[e-mail]>
Subject:      Re: Access Performance

On Tue, 4 May 1993 13:38:09 -0700, Bill Stewart wrote:

>I am in the process of developing(99% done) a database to track the
>location and specifications of computer hardware on our campus.  I have
>over 4300 records in the database and I'm running on a 66Mhz DX2.  The
>performance in Access is pretty zippy.
>
>I've run the same data base on a 386 16Mhz IBM PS/2 Mod 55 and found the
>performance a little less that desired. I'm wondering what expirences any
>of you might be having running large data bases on various CPU classes and
>clock speeds?
>

Most of our machines are IBM PS/2 Mod 55 (16 MHz with 4 Mb of memory) and,
yes, the performance could be better. At first the smartdrive size was
1024, but reducing it to 512 helped significantly. I'm just afraid that
there's not very much to do.

Pekka

P.S. It's little out of the scope of this list, but is there any way to
     upgrade those Mod 55's? Any non-Intel chips that you could plug in?
     Or can you change the mother board (or does the microchannel
     architecture prevent that?)?).

:) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :)

    _/_/_/_/   _/   _/_/  _/_/  _/_/_/_/   "Any sufficiently advanced
   _/    _/   _/   _/ _/_/ _/  _/    _/           technology is "
  _/         _/   _/      _/  _/    _/   indistinguishable from magic."
 _/    _/   _/   _/      _/  _/    _/             (A. Clarke)
_/_/_/_/   _/   _/      _/  _/_/_/_/

Pekka Koskinen    tel [phone]    fax [phone]
CIMO, P.O. Box 343, 00531 Helsinki, FINLAND
=========================================================================
Date:         Wed, 5 May 1993 09:46:36 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Re: Page Numbering

Thanks Amy for your hint (="Page " & Page & " of 5"),

but your method only works if I know how many pages will come. If the
report is 5 pages now and 10 pages tomorrow it couldn't work.

In Excel there are two "switches": &P printes the current page-number and
&A printes the number of all pages.

It seems that there isn't a similar thing in Access.

Anymore ideas?

Regards

Martin
=========================================================================
Date:         Wed, 5 May 1993 12:12:31 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Memory-problems, too many tables

Hi again!

Besides this lousy page-numbering problem we have encountered the following
problems:

We have about 22 DBF-tables bound-in (not imported!!!) and about the same
number of tables and we get frequent "Not enough memory" and "Not more
tables can be opened" messages (we have the german version of Access so the
English messages may be a bit different!!).

MS-Hotline in Munich told me that the amount of fields and the number of
bound tables costs very much memory (the tables have about 10 to 50 fields
but only some test-records).
The .MDB-file is about 250 kB (after compressing it) to 500 kB.

Any ideas? Will Access 1.1 solve these problems?

Regards

Martin
=========================================================================
Date:         Wed, 5 May 1993 06:12:46 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: Access Performance

It sounds like there are quite a few different results on the speed
performance for Access.  I wonder if there is any sort of bechmark tests
to run to see if FoxPro is actually faster than Access?  I wonder what the
industry standrard benchmark test is, if any?

I think Access is quite flexable and easy to get started with.  I have only
limited expirence with FoxPro and came to the conclusion that it just
wasn't what I wanted.  I wonder if the next version of Access might have
the FoxPro routines that make it run quicker.  One can only hope.

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
_________________________________________
=========================================================================
Date:         Wed, 5 May 1993 07:29:49 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: Access Performance

I'm curious, how were you performiong your lookup?  I've found that using a
filter is tremendously quicker that using the FindRec or table.Seek methods.

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
_________________________________________
=========================================================================
Date:         Wed, 5 May 1993 16:30:50 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Re: Access Performance

Hi to all on Access-l and MS-Access!

Access is a lot slower than nearly all other databases.

The speedwinner in a recent PC-Magazine test was FoxPro 2.5 for Windows
which was faster than Paradox for DOS and of course faster than all other
Windows-XBase-systems. The last PCMag also compared dBase IV 2.0 for DOS
with other XBase-systems.

I guess Access was never meant to be a speedy database product.
=========================================================================
Date:         Wed, 5 May 1993 07:39:50 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: Access Performance

Do't give up on it yet.  It's only version 1.0, and pretty impressive for
the first release.

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
______________________
=========================================================================
Date:         Wed, 5 May 1993 09:33:28 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Access Performance
In-Reply-To:  Message of Wed, 5 May 1993 16:30:50 CET from <[e-mail]>

Well, gee...if you're running it on an i486DX-66 with a math coprocessor
and 16 megs of RAM and a Windows video accellerator card, I imagine Access
would be a pretty good performer...:)  (And just wait for Pentium! *grin*)

Seriously, when I attended the last Microsoft seminar here, they were
rather "up-front" about the fact that Access was primarily meant for
smaller databases, while FoxPro was their "power-user" database.  Someone
mentioned a few messages back that Access makes it possible for users
to get at their data with ease and that the speed sacrifice was worth
it if you could just get at your data.  I concur with that sentiment--
even though I was not having major problems with dBase IV, I've made
the conversion to Access without much trouble because I needed a
Windows-based solution to my DBMS system.  HOWEVER I have to say that
none of my databases are over 1000 records in length (yet).

Like they say on the network news, "time will tell."

Nathan

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Wed, 5 May 1993 09:39:00 CST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         E'ci <[e-mail]>
Subject:      Importing text files

Greetings,

I need to import some really HUGE datasets that are in fixed width format.
Accompanying them are files that possess the name, type, length, start and stop
columns. Is there a way (once the file is properly massaged) to import or
copy this file to the Import/Export Specification? One of the files has
345 fields and I do not want to do it by hand. Any ideas?

Due to the size of this project, I should probably use FoxPro-Win, but I have
Access and I like it.

Any help would be greatly appreciated.


Tod R. Massa
[e-mail]
=========================================================================
Date:         Wed, 5 May 1993 07:43:38 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jimmy Lew <[e-mail]>
Subject:      Re: Access Performance
In-Reply-To:  <no.id>; from "Pekka Koskinen CIMO" at May 5, 93 8:08 am

>
> On Tue, 4 May 1993 13:38:09 -0700, Bill Stewart wrote:
>
> >I am in the process of developing(99% done) a database to track the
> >location and specifications of computer hardware on our campus.  I have
> >over 4300 records in the database and I'm running on a 66Mhz DX2.  The
> >performance in Access is pretty zippy.
> >
> >I've run the same data base on a 386 16Mhz IBM PS/2 Mod 55 and found the
> >performance a little less that desired. I'm wondering what expirences any
> >of you might be having running large data bases on various CPU classes and
> >clock speeds?
> >
>
> Most of our machines are IBM PS/2 Mod 55 (16 MHz with 4 Mb of memory) and,
> yes, the performance could be better. At first the smartdrive size was
> 1024, but reducing it to 512 helped significantly. I'm just afraid that
> there's not very much to do.
>
> Pekka
>
> P.S. It's little out of the scope of this list, but is there any way to
>      upgrade those Mod 55's? Any non-Intel chips that you could plug in?
>      Or can you change the mother board (or does the microchannel
>      architecture prevent that?)?).
>
> :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :)
>
>     _/_/_/_/   _/   _/_/  _/_/  _/_/_/_/   "Any sufficiently advanced
>    _/    _/   _/   _/ _/_/ _/  _/    _/           technology is "
>   _/         _/   _/      _/  _/    _/   indistinguishable from magic."
>  _/    _/   _/   _/      _/  _/    _/             (A. Clarke)
> _/_/_/_/   _/   _/      _/  _/_/_/_/
>
> Pekka Koskinen    tel [phone]    fax [phone]
> CIMO, P.O. Box 343, 00531 Helsinki, FINLAND
>

IBM is offering a 486slc2 processor upgrade.  Its part number is
32g2606.  The clock speed is 50 MHz.  The chip plugs into the mother
board without taking up a slot.

jlew
=========================================================================
Date:         Wed, 5 May 1993 08:13:29 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: Importing text files

One way to import data is to use the Import/Export option in the File Menu.
It will import fixed width files as well as several others.

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
_________________________________________
=========================================================================
Date:         Wed, 5 May 1993 10:54:05 CDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         randy legeai <[e-mail]>
Subject:      Re: Importing text files
In-Reply-To:  <[e-mail]>; from "E'ci" at May
              5, 93 9:39 am

> I need to import some really HUGE datasets that are in fixed width format.
> Accompanying them are files that possess the name, type, length, start and
 stop
> columns. Is there a way (once the file is properly massaged) to import or
> copy this file to the Import/Export Specification? One of the files has
> 345 fields and I do not want to do it by hand. Any ideas?
>
Robert:  I recently imported a very large fixed-length file from a
SAS database.  Use the Wizard for import/export.  I did manually
enter fieldnames, starting positions, and length, but that was
pretty quick, especially since I didn't need (and therefore didn't
import) all of the fields.  The original file was around 500K.

--
Randall Legeai                             [e-mail]
Federal Agency Affairs / Ctr. Bioenv. Research      Phn: 504/865-5758
327 Gibson Hall, Tulane University                  Fax: [phone]
New Orleans, Louisiana 70118-5698
=========================================================================
Date:         Wed, 5 May 1993 11:09:00 CDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Miguel Rivera <[e-mail]>
Subject:      Re: Access Performance

> Hi to all on Access-l and MS-Access!
>
> Access is a lot slower than nearly all other databases.
>

You cannot compare DOS databases with windows databases. The power
that windows offer and the overhead of the grphical environment make
a direct comparison very difficult.

> The speedwinner in a recent PC-Magazine test was FoxPro 2.5 for Windows

Fox Pro for windows is a direct port from it DOS version. I don't consider
FOX Pro as a truly windows DB. It lacks from many features that windows
provides and is not as EASY to use than Access, but is it faster.

There is a rumor than Microsoft would eventually put the propietary
Fox Pro DB engine into Access. I would like to see that done soon.
They eventualy would like to support only one DB package. Like I
said, this is a rumor and I am passing it as is.

> which was faster than Paradox for DOS and of course faster than all other
> Windows-XBase-systems. The last PCMag also compared dBase IV 2.0 for DOS
> with other XBase-systems.
>
> I guess Access was never meant to be a speedy database product.

Be patient, you are working with version 1.0. As a software engineer,
I am very surprised with the quality of the product. I have not
found any major bug during the development of my applications.

I think Access is a very good database compared to Paradox for windows.
Paradox claim to be a lot faster than Access but it is not (base on
review and benchmarks by different magazines). I think that Microsoft
has done a fine job putting a well defined and extremely EASY to use
DBMS available to users to fulfill the needs of the most common DB
applications.

I don't think that Access will replace any SQL server yet. There
is a lot of room for improvement. If speed is the main concern,
I think Access (Version 1.0) is not the right choice. If you want
to prototype applications, write small to medium DB systems, and
test your relational design, I guess access is an excelent tool.

IMO, I think is worth to wait for the new version of Access which is
coming soon. If you have your copy registered, you will receive
information about your upgrade and you will pay only the cost of the
materials.

I have worked with many DBMS including INGRES, INFORMIX, ORACLE, dBase III
and IV, 4 Dimension (MAC) and I think Access is the EASIEST to use among all
of them.

I hope this helps to clarify some of the questions about Access,


Miguel A. Rivera
AT&T Bell Labs.
Naperville, IL. 60563
=========================================================================
Date:         Wed, 5 May 1993 11:22:27 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: Alpha Phi Omega, Tau Omicron Chapter
Subject:      Re: Access Performance
In-Reply-To:  Message of Wed,
              5 May 1993 11:09:00 CDT from <[e-mail] M>

I don't think that "rumor" about Fox and Access being together in one
package is really a rumor.  I heard an MS representative say just that at
a Microsoft seminar in January.  But he <did> say that this is a project
that may take 6-10 years and we shouldn't look for it anytime soon.

Whether or not it ever happens is another story.

Nathan
=========================================================================
Date:         Wed, 5 May 1993 10:25:02 MDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     Converted from PROFS to RFC822 format by PUMP V2.1
From:         "Brian Keeler (403) - 471-8623" <[e-mail]>
Subject:      Importing text files
In-Reply-To:  note of 93-05-05 08:54

I have imported flat text (ascii) files from our VAX 6420 using the
import delimited file option, and it works great.. The fields are
delimited with semi colon (;), you can use any character, but you must
set up your import files thru the options part after selecting IMPORT
from the main menu item in FILE.. hope this helps you out..

Brian Keeler    (403) - 471-8623   ..What is a CD-ROM ??
Application Services Coordinator     3 billion pits arranged
Information Services Division        in a 3 mile spiral..
domain: [e-mail]
=========================================================================
Date:         Wed, 5 May 1993 17:07:48 BST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Anne L Zorner R27.G5/" <[e-mail]>
Subject:      Access security workings

SQL Support Section (SQS)         Mail [e-mail]
===============================================================
Dear Access friends
I wonder whether anyone else has noticed / experienced a problem
that I seem to be having.

I have a Novel network where I want to store a database. I also wanted
to associate with it a workgroup, so I copied the system.mba file
over into the same directory. All users on the network may have
their own copy of access, they can obviously create their own databases
on their own pc.

The thing is, if a user has access on a local PC for which he is
a user and he uses his local system.mba rather than the workgroup
system.mba on the network that I have set up he suddenly has full admin
rights on the remote database as well. Is it tru that if you are an
admin user in your own local database then you immediately are an
admin user in any other database that you have access to (excuse the pun)
or have I missed some bit of security somewhere?

Can I people opening that database unless they have connected to the
correct workgroup?
Anne

Thankyou
===============================================================
=========================================================================
Date:         Wed, 5 May 1993 11:12:13 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Henry Unger <[e-mail]>
Subject:      Page Numbering
In-Reply-To:  "Hilger Martin Dr."'s message of Wed,
              5 May 1993 09:46:36 CET <[e-mail]>

In order to print Page 1 of N you need to know in advance how
many pages there will be, which is difficult in a database but
easy in a spreadsheet.  In a multi-user database it is possible
for the number of pages to change during the production of the
report as new records are added to the database, rendering a
non-deterministic problem.
=========================================================================
Date:         Wed, 5 May 1993 11:58:43 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Re: Don't use = with RunCode

>
>
>  > To my amazement, I see that the Action gets executed before the conditional
>  > expression is executed! After much debugging (and frustration, since the
>  > Action was to delete some records), I found that if you define an Action
>  > that executes "RunCode" and specifies the function with =FunctionName(),
 this
>  > improper behavior occurs. If you specifiy the function name (operand of
>  > the RunCode action) without the preceding '=' (equal sign), then everything
>  > works as expected.
>
>       This very much makes sence!  What you were asking Access to do was
>       to execute function FunctionName() and then performe action RunCode
>       using as an argument whatever the FunctionName() returned.
>       I also remember reading someting about the evaluating of things in
>       macros' conditinos no metter if condition is false or true. I think
>       in Basic it is different.
>
>       Dmitry Serebrennikov     [e-mail]
>

Here's what I was trying to do:

Macro Name          Condition                 Action
----------          ---------                 ------

Delete              CheckDelete()             RunCode
 =DeleteOrder([OrderNumber])

The idea was that if CheckDelete() returned nonzero, then I wanted to execute
the action (which was to DeleteOrder). Dmitry suggested that Access was
 executing
DeleteOrder (because of the equal-sign '=') and then performed action RunCode
using as an argument whatever DeleteOrder() returned. The problem is that
DeleteOrder returns a long and that should (hopefully?) cause access to complain
about trying to execute a long since the actual value was zero. [Dmitry: I agree
with your analysis of what Access should do with that expression. But, I don't
see that Access is indeed doing that.]

What I thought was incorrect was that Access executed DeleteOrder without
evaluating the CheckDelete() condition. I understand that Access macros (like
many languages) do not guarantee an ordering of evaluation for conditional
expressions that involve executing functions. But, Access is doing something
much worse; it executes the action (or an operand of an action) before
 evaluating
ANY of the conditions.

I'm making a big deal of it because:
  1) I don't want any of you guys to waste alot of time trying to figure out
     this problem again. These kind of subtle problems can be difficult to
     figure out.
  2) I want Microsoft to fix this problem since it seems incorrect to execute
     an action or any operand of an action without first checking the conditions
     first.


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Wed, 5 May 1993 15:02:08 CST
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "John A. Olson" <[e-mail]>
Subject:      Don't use = with runcode

I have a question for you.  Why is function CheckDelete() returning a
numeric value?  You should have it return either TRUE or FALSE.  That way,
in your condition statement it will only execute if it comes back as
TRUE.  I'm not sure, but I think ACCESS treats any numeric value as TRUE.

Try this in your function CheckDelete():

Function CheckDelete()

CheckDelete = FALSE

If (some condition) Then
CheckDelete = True
Exit Function

End If

End Function

This should help I hope!

John

[e-mail]
=========================================================================
Date:         Wed, 5 May 1993 14:46:49 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Re: Don't use = with runcode

> I have a question for you.  Why is function CheckDelete() returning a
> numeric value?  You should have it return either TRUE or FALSE.  That way,
> in your condition statement it will only execute if it comes back as
> TRUE.  I'm not sure, but I think ACCESS treats any numeric value as TRUE.
>
> Try this in your function CheckDelete():
>
> Function CheckDelete()
>
> CheckDelete = FALSE
>
> If (some condition) Then
> CheckDelete = True
> Exit Function
>
> End If
>
> End Function
>
> This should help I hope!
>
> John
>
> [e-mail]
>

Actually, I looked and could not find what the valid symbolic names for
TRUE and FALSE. I did find others, just not the ones that I was looking for.
Anyway, I know that Access treats non-zero values as TRUE and zero values as
FALSE so I made my function return one and zero, respectively (I think that
Access uses -1 for TRUE, though).

I tested using CheckDelete in a dummy macro to be sure that when returning one,
Access executed the specified action(s). When specifiying a RunCode action with
a function name starting with and '=', the wierdness begins. Without the '=',
Access will correctly interpret the condition and execute the action
 accordingly.
With an '=' starting the operand of the RunCode action, Access executes the
operand first, then interprets the condition.

I don't think this problem goes away whether I use TRUE/FALSE or 1/0.


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Wed, 5 May 1993 23:51:29 +1000
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         /R=ECC/R=AM/U=IT_GREG/FFN=IT_GREG/@MR.TASED.EDU.AU
Subject:      Re: Access Performance
In-Reply-To:  <01GXUN3X3R0495MS56*@mr.tased.edu.au>

Bill Stewart,

The  list was through a form and a combo box. The resulting pop-up pick
list (~13000 record table)  required a value from the table.

Greg Curtis
Dept of Education and the Arts
Tasmania
Australia
=========================================================================
Date:         Thu, 6 May 1993 00:02:47 +1000
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         /R=ECC/R=AM/U=IT_GREG/FFN=IT_GREG/@MR.TASED.EDU.AU
Subject:      Re: Access Performance
In-Reply-To:  <01GXUNHYXCX095MS56*@mr.tased.edu.au>

I agree that development in Access is initially easier than many other
systems, but it does not take a great time to become proficient at any of
the languages/systems.

The two factors that should be more significant, for professional
programmers, are
     - the power of the language to simply achieve complex tasks. Here
access performs well, but still lacks the plethora of third pparty add-ons
that Clipper and FOX enjoy.
      - the ease of maintenance. This is where I think Access falls down
somewhat, mainly because of the variety of ways of achieving an end. It
can be very difficult to follow how an application flows because all the
program is not in front of you. You have to search tables, queries, macros,
modules and menu options to find what is really happening. This may be
ok where site standards set the rules, but where clients are developing
themselves this could become a problem for future maintenance.

Greg Curtis
Dept of Education and the Arts
Tasmania
Australia
=========================================================================
Date:         Wed, 5 May 1993 20:29:42 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Dan Tauber <[e-mail]>
Subject:      Record locking in joins
In-Reply-To:  <no.id>; from "Jim Renaud" at May 5, 93 2:46 pm

I'm having a problem with joins (actaully, after talking to a Borland Paradox
engineer, I think it is a feature of Access' data model).  When I create
a join, Access locks the entire record in the master table, it doesn't allow
editing of any of the data. I understand why Access would lock the key field,
having the hash values change in the middle of a join would be a pain to
deal with from a programmer point of view. But, it locks the entire record,
not just the linked field.

Does anyone have a work-around for this? I'd like to have a form based on
a one-to-one join that allows editing of both tables.

I talked to a MS person about this and he said it did not lock the entire
record, only the key and linked fields but then he tried it and couldn't
explain why it didn't work.

The Borland person I talked to said it was due to the embeded form data model
that Access uses. Paradox used to have the same problem but they have moved
to a new data model in Paradox for Windows.
=========================================================================
Date:         Thu, 6 May 1993 08:51:18 -0400
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         R Hyde <[e-mail]>
Subject:      Re: Access Performance
In-Reply-To:  <[e-mail]>

On Tue, 4 May 1993, Bill Stewart wrote:
>
> Has anyone herd when the run-time module for Access will be released?

When I spoke to a Microsoft (Canada) customer service rep. a couple of
days ago she said "two months".

Bob Hyde
[e-mail]
=========================================================================
Date:         Thu, 6 May 1993 07:48:07 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Morris Myers <[e-mail]>
Subject:      Microsoft Access 1.1

This information was sent to me by a friend. he found it on
the net somewhere.


----- Begin Included Message -----

Picked up a flyer about Microsoft Access version 1.1 yesterday at the
Microsoft Booth at DB/EXPO 93, and I thought I'd share.

Typos are mine, I don't work for MS, etc., etc., etc.

[snip]

Microsoft Access(r)
Relation Database Management System for Windows(tm)
version 1.1

Microsoft Access now works with more data formats for greater
information access

 Users and corporations have large investments in existing data and, as a
 result, they require a powerful database that works with a variety of desktop
 and client-server environments.  To help preserve these investments, Microsoft
 Access version 1.1 now allows users to operate openly against an even greater
 variety of data sources, making it easier for end users to get at the data.
 Whether on a workstation, across a network, or in a client-server
 configuration, Microsoft Access lets users share data easily, even if they
 are using different database products.

Microsoft Access version 1.1 offers:

 Direct connectivity to read and write Oracle(r) data through Open Database
  Connectivity (ODBC)

 Direct connectivity to read and write SYBASE(r) SQL Server data through ODBC

 Direct connectivity to Microsoft FoxPro(r) 2.0 and 2.5 data and indexes.

 A new, more robust ODBC driver to Microsoft(r) SQL Server, using fewer
  connections and operating faster than Microsoft Access 1.0

 Faster and more flexible fixed-width importing, including support for
  variable lengths.

 Improved support for Btrieve(r) data--the INDEX.DDF file is no longer
  required to be able to read Btrieve .DAT files.

 Easier importing of Microsoft Excel database named ranges

 A new export option for moving data into Word for Windows Mail Merge format

 Various additional data access enhancements.  For instance, users of
  Microsoft Access 1.1 can attach to Paradox(r) tables that are currently in
  use and can attach to dBASE files on a CD

Additional enhancements in Microsoft Access version 1.1

 The maximum database file size has increased from 128MB to 1 gigabyte

 Third-party add-in wizard products are now easier to install, allowing users
  to take advantage of the growing third-party tool market for better
  productivity

 Various other small enhancements at the request of customers.

Upgrade information

 Microsoft Access version 1.1 is scheduled to be available through resellers or
 direct from Microsoft in the spring of 1993.  The cost of the upgrade is
 essentially the cost of materials--$14.95 (suggested retail price) from
 resellers.  (Add $5.00 freight when purchased directly from Microsoft.)
 Because of the importance of access to data, the Microsoft Acccess 1.1 license
 and software allows customers to copy the Microsoft Access version 1.1 upgrade
 onto any machine with 1.0 installed at no additional cost.

_____________________________________________________________________________
Microsoft and FoxPro are registered trademarks and Microsoft Access and
Windows are trademarks of Microsoft Corporation.  Oracle is a registered
trademark of Oracle Corporation.  SYSBASE is a registered trademark of
Sybase, Inc.  Parados is a registered trademark of Borland, International.
Btreive is a registered trademark of Novell, Inc.

End of forwarded message.


----- End Included Message -----
=========================================================================
Date:         Thu, 6 May 1993 09:54:42 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Microsoft Access 1.1
In-Reply-To:  Message of Thu,
              6 May 1993 07:48:07 PDT from <[e-mail]. COM>

In essence, licensed users got this information about a week or so ago...
there was a letter and a survey and some other information sent out by
the Access team (at least, <I> got it!).

I'm impatiently waiting....:)

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Thu, 6 May 1993 17:00:26 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Opening Reports

Hi to all on Access-l and MS-Access!

I set the rights of opening a report to read-only.
When I open the report there's always a message saying
"The report is read-only. Open it for read-only? OK Cancel Help"

As it seems one has to open a report with write-rights:

DoCmd OpenReport report [, view] [, filter] [, cond]

Does anybody have a hint for me?

Thanks in advance

Martin
=========================================================================
Date:         Thu, 6 May 1993 10:39:30 CST
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "R. D. McClary" <[e-mail]>
Subject:      Re: Microsoft Access 1.1

In Message Thu, 6 May 1993 09:54:42 EST,
  Nathan Brindle <[e-mail]> writes:

>In essence, licensed users got this information about a week or so ago...
>there was a letter and a survey and some other information sent out by
>the Access team (at least, <I> got it!).
>

SO WHERE THE (BLEEP) IS OURS?  Our group has 3 registered copies and have
yet to hear diddly from MS!  (PS - any idea when it will be "available from
resellers" in Central Illinois?  Thanks.)
[][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][]
               /|              []
            ` o.O '            []   [e-mail]
            =(___)=            []   R. D. McClary
               U               []   Department of Plant Pathology
          ACK!THPTPHH!         []   University of Illinois, Urbana-Champaign
[][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][]
=========================================================================
Date:         Thu, 6 May 1993 09:08:38 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Info on Access v1.1

From a colleague of mine...

----- Begin Included Message -----

Picked up a flyer about Microsoft Access version 1.1 yesterday at the
Microsoft Booth at DB/EXPO 93, and I thought I'd share.

Typos are mine, I don't work for MS, etc., etc., etc.

[snip]

Microsoft Access(r)
Relation Database Management System for Windows(tm)
version 1.1

Microsoft Access now works with more data formats for greater
information access

 Users and corporations have large investments in existing data and, as a
 result, they require a powerful database that works with a variety of desktop
 and client-server environments.  To help preserve these investments, Microsoft
 Access version 1.1 now allows users to operate openly against an even greater
 variety of data sources, making it easier for end users to get at the data.
 Whether on a workstation, across a network, or in a client-server
 configuration, Microsoft Access lets users share data easily, even if they
 are using different database products.

Microsoft Access version 1.1 offers:

 Direct connectivity to read and write Oracle(r) data through Open Database
  Connectivity (ODBC)

 Direct connectivity to read and write SYBASE(r) SQL Server data through ODBC

 Direct connectivity to Microsoft FoxPro(r) 2.0 and 2.5 data and indexes.

 A new, more robust ODBC driver to Microsoft(r) SQL Server, using fewer
  connections and operating faster than Microsoft Access 1.0

 Faster and more flexible fixed-width importing, including support for
  variable lengths.

 Improved support for Btrieve(r) data--the INDEX.DDF file is no longer
  required to be able to read Btrieve .DAT files.

 Easier importing of Microsoft Excel database named ranges

 A new export option for moving data into Word for Windows Mail Merge format

 Various additional data access enhancements.  For instance, users of
  Microsoft Access 1.1 can attach to Paradox(r) tables that are currently in
  use and can attach to dBASE files on a CD

Additional enhancements in Microsoft Access version 1.1

 The maximum database file size has increased from 128MB to 1 gigabyte

 Third-party add-in wizard products are now easier to install, allowing users
  to take advantage of the growing third-party tool market for better
  productivity

 Various other small enhancements at the request of customers.

Upgrade information

 Microsoft Access version 1.1 is scheduled to be available through resellers or
 direct from Microsoft in the spring of 1993.  The cost of the upgrade is
 essentially the cost of materials--$14.95 (suggested retail price) from
 resellers.  (Add $5.00 freight when purchased directly from Microsoft.)
 Because of the importance of access to data, the Microsoft Acccess 1.1 license
 and software allows customers to copy the Microsoft Access version 1.1 upgrade
 onto any machine with 1.0 installed at no additional cost.

_____________________________________________________________________________
Microsoft and FoxPro are registered trademarks and Microsoft Access and
Windows are trademarks of Microsoft Corporation.  Oracle is a registered
trademark of Oracle Corporation.  SYSBASE is a registered trademark of
Sybase, Inc.  Parados is a registered trademark of Borland, International.
Btreive is a registered trademark of Novell, Inc.


----- End Included Message -----



-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Thu, 6 May 1993 12:19:48 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Rob Cermak <[e-mail]>
Subject:      DDE Conversation

Hi,
        I'm interested in obtaining some code for Visual BASIC Windows 2.0
        in creating a DDE conversation to Microsoft Windows Access.  In
        particular when you have a table setup, I want to insert data
        into a particular record.

        I'm fairly familiar with the code, but someone could help
        me out with providing the LinkTopic & LinkItem and if I
        should be using LinkSend or LinkPoke in a Manual DDE link
        conversation with Microsoft Windows Access.
Thanks,
        Rob Cermak
=========================================================================
Date:         Thu, 6 May 1993 11:24:23 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Microsoft Access 1.1
In-Reply-To:  Message of Thu,
              6 May 1993 10:39:30 CST from <[e-mail].E DU>

On Thu, 6 May 1993 10:39:30 CST R. D. McClary said:
>
>SO WHERE THE (BLEEP) IS OURS?  Our group has 3 registered copies and have
>yet to hear diddly from MS!  (PS - any idea when it will be "available from
>resellers" in Central Illinois?  Thanks.)

I don't know and I don't know....I wish I did.  If I had the thing with me
I'd post the high points, but it fell victim to a briefcase clearing this
morning and is sitting on my desk at home.

If there are still some MS folk on here, maybe they can comment?????

--Nathan

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Thu, 6 May 1993 10:03:20 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> W: SUBJECT field duplicated. Last occurrence was
              retained.
From:         Dustin Kassman <[e-mail]>
Subject:      Re: NEED: ACCESS standards document

The charter issue of Smart Access has an article which proposes a
standard for naming objects in Access.  The naming conventions are
based on a method of naming called Hungarian, which Microsoft uses
internally.  The authors claim a naming convention will make it easier:
to maintain Access programs, to share code among developers, and to get
help from other developers.

The conventions looked pretty senible to me and I plan to use them in my
development.  I received the charter issue of Smart Access as an evaluation
copy and I am sure anyone who is interested can get a copy from the publisher.

Smart Access (ISSN #1066-7911) is published by Pinnacle Publishing, Inc.,
18000 72nd Avenue South, Suite 217, Kent, WA 98032.  Special requests may
be sent to The Editor, Smart Access, PO Box 888, Kent, WA 98035-0888.
Their phone numbers are [phone] or [phone].  Email requests
can be sent to CompuServe 76447,417.  They request you allow two days for
an email response.

----

Dustin Kassman                  [e-mail]                 Corvallis, Oregon
=========================================================================
Date:         Thu, 6 May 1993 19:27:27 -0500
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         George Raudabaugh <[e-mail]>
Subject:      Import var records/how?

I'm trying to import records that have several fixed fields followed
by one variable length one.  There is no delimeter to choose from.

What happens is Access imports the first record but includes parts of
the second record since the var field of the first record is shorter
than what I specified to access.

I've gotten around this previously by padding the individual records
out with blanks in another file.  I canned the program some time back
so would like advice if there is a better way to do this.  (or I'll
end up rewriting the program again :(  ).

GR
--
George Raudabaugh               Manager/Document Technologies
Information Dimensions, Inc.    [e-mail] (work email)
5080 Tuttle Crossing Blvd.
Dublin, Ohio  43017             [phone]                     (voice mail)
=========================================================================
Date:         Thu, 6 May 1993 17:58:28 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "ROBERT GRINNELL,
              SEATTLE PACIFIC UNIVERSITY" <[e-mail]>
Subject:      Re: Import var records/how?

On Thu, 6 May 1993 19:27:27, George Raudabaugh writes:

>I'm trying to import records that have several fixed fields followed
>by one variable length one.  There is no delimeter to choose from.

>What happens is Access imports the first record but includes parts of
>the second record since the var field of the first record is shorter
>than what I specified to access.

>I've gotten around this previously by padding the individual records
>out with blanks in another file.  I canned the program some time back
>so would like advice if there is a better way to do this.  (or I'll
>end up rewriting the program again :(  ).

It sounds like version 1.1 will handle this when it comes out, but
until then you will need some kind of routine to either pad the records
or import the file "manually" using the direct file access statements
like Open and Get.

Robert Grinnell
Seattle Pacific University
[e-mail]
=========================================================================
Date:         Fri, 7 May 1993 14:29:43 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Shannon Burgin <##[e-mail]>
Subject:      Help

I am stuck on a data sheet and cannot find the appropriate value to
enter on the field.  'Esc' did not work.  I keep getting the message
about cannot save a record with a null value as part of the key (this
field ispart of the key).How do I get out of the data sheet?


************************************************************************
*                                *                                     *
* Shannon Burgin                 *    University of Tennessee/Martin   *
* Bitnet: ##[e-mail]    *    Computer Center                  *
* Phone: [phone]            *    102 Cooper Hall                  *
* Senior Systems Analyst         *    Martin, TN 38238                 *
* VM/VSE/CICS/VSAM/DLI/SQLDS     *                                     *
************************************************************************
=========================================================================
Date:         Fri, 7 May 1993 13:42:05 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Re: Help

>
> I am stuck on a data sheet and cannot find the appropriate value to
> enter on the field.  'Esc' did not work.  I keep getting the message
> about cannot save a record with a null value as part of the key (this
> field ispart of the key).How do I get out of the data sheet?


I don't know if this works from the datasheet view, but I normally just
double-click on the upper left box (which does a close). It will complain about
the null value. After clicking on OK, double-click on the upper-left box (again
it does a close) immediately and it will say something about record could not
be saved. I do this in form view of a form. I have not tried it in datasheet
view, though.


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Mon, 10 May 1993 13:39:45 -0800
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "David L. Finley" <[e-mail]>
Subject:      Database "Locked-Out"

I have encountered a database "lockout" problem. In particular, I had a
"large" database (due to use of OLE items and bitmaps) which I
"cleaned-up" and compressed. After the compression, the data-object
permissions for the tables, queries, macros, and modules were set such
that I could not read or use them (btw, I was running in "unsecured
mode").

I set up myself as "Admin", which I understand should give me _FULL_
privileges to modify any/all data-object permissions. Unfortunately,
even _then_ I was refused permission to modify permissions.

Does anyone have any suggestions on how I might "access" my locked-out
database? I have some work I would like to recover.

Dave F.
[e-mail]
=========================================================================
Date:         Tue, 11 May 1993 09:30:37 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Pekka Koskinen CIMO <[e-mail]>
Subject:      Calculated field in a select query & file sizes

Hello Access-folks!

I'm trying to do the folliwing (without luck):

I have a table with peoples names and their permanent addresses (lets call
it [ADPERM]) and people's temporary addresses (lets call it [ADTEMP]). In
the perm. address fiels there is always an address, but not always in the
temp. address field. But, if there is something in [ADTEMP], I want to use
that one instead of the permanent one.

So, I'm trying to make a select query with a calculated field. In the first
line ("fied") I have the following expression:

     ADR: IF [ADTEMP] IS NULL THEN ADR=[ADPERM] ELSE ADR=[ADTEMP]

Actually I've tried several versions of the previous, but the result is
always the same: SYNTAX ERROR! Too bad...

So, what am I doing wrong? Is it not allowed to use "if...then...else..."
-statement?

Or am I stupid or what?... So far the only way I've been able to
accomplish this is to make an extra field and run two update queries using
the info of my "if...then...else..." -statement in "criteria" and "update
to". But I'd like to perform the task easier and faster. (of course I could
make a macro...).


Then there's an interesting thing I just noticed: I had a database with
quite a few tables and records, the whole database -file size being about
3 Mb. Then I deleted most of the tables and expected the file size to
reduce to less than 1 Mb, but nothing happened! The database has perhaps
one tenth of the records in the original one, but it's still of the same
size!

Am I again dummy or is Access, which is dummy? Am I doing something wrong?


If someone can give me some hints of my problems, I'd appreciate it. In the
meantime, best wishes from sunny Helsinki!

Pekka

:) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :)

    _/_/_/_/   _/   _/_/  _/_/  _/_/_/_/
   _/    _/   _/   _/ _/_/ _/  _/    _/   "Suffer fools gladly;
  _/         _/   _/      _/  _/    _/      they may be right"
 _/    _/   _/   _/      _/  _/    _/         (H. Jackson)
_/_/_/_/   _/   _/      _/  _/_/_/_/

Pekka Koskinen    tel [phone]    fax [phone]
CIMO, P.O. Box 343, 00531 Helsinki, FINLAND
=========================================================================
Date:         Tue, 11 May 1993 11:57:04 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Re: Database "Locked-Out"

Hi Dave, hi to all on ACCESS-L and MS-ACCESS!

I also have encountered problems with being "locked out", even as Admin.
There must be some bugs in the administration of rights.

I solved it by saving the object (whatever it was!) under a different name
and then saving it again under the first name. Then I deleted the new name
again and voila: I could do everything again.

There's another one: when opening a report via Access Basic when I had just
read-rights there's ALWAYS a messagebox saying: "The object is
write-protected. Open read-only? Yes No Cancel"

But there MUST be a chance to open a report without having the permission
to change this object, or am I wrong??

Regards

Martin
=========================================================================
Date:         Tue, 11 May 1993 14:15:03 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Sorting in Reports

Hi to all on Access-L and MS-Access!

Is there any way to sort records in a report in a way that I can change
dynamically?
Can I change the sort-options via Access Basic?

To my opinion there should be a way to do this WITHOUT having rights to
change a report, it should be possible to chnage sort-properties at
run-time.

If this isn't possible it means that I have to dozens of versions of the
same report just to have different sortings.

Any hint greatly appreciated!!

Martin
=========================================================================
Date:         Tue, 11 May 1993 06:21:57 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: Calculated field in a select query & file sizes

I'm not sure why your query isn't working properly.  I've kind of started
to move to using Access BASIC(AB) to do things like you had described.  I'm
finding out that AB is tremendously quicker than running the same thing in
a query.

The reason your database didn't reduce in size after deleting records is
due to the way Access, or databases in general, handles deletes.  When a
record is deleted the data is not stripped away from your datafile.
Instead it is marked as not being able to be displayed.

To get your file to reduce in size you will probably need to run the
compact menu option. I've also noticed that after making changes/developing
a database it grows a little in size.  This is due to objects being marked
as deleted, but not removed.  I can get the size down again by running the
compact option.

Good Luck with your Query

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
_________________________________________
=========================================================================
Date:         Tue, 11 May 1993 06:52:12 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Command Button Tip

Just thought I'd pass on a tip to help save some time working with command
buttons.

I've developed a screen with some 'sunken' boxes that have three lines of
data in them.  The first line of data is an indexed value to a record.  I
wanted to be able to double click on the box to jump to the record.  I had
the code all set, but when I replaced the box with the command button and
switched to dataview the button came to the front.  Selecting the button
and using the send to back command didn't even help.  The button kept
coming to the front.  The fix I finally stumbled upon was to set the
command buttons transparent property to 'YES', and put back the sunken in
box.  Works great!

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
________________________________________
=========================================================================
Date:         Tue, 11 May 1993 16:01:45 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      file sizes

I run this compressing option in the file menu quite often. It reduces the
size of the database by a very high percentage and everything works faster
for a while.
=========================================================================
Date:         Tue, 11 May 1993 07:55:29 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Re: Calculated field in a select query & file sizes

>
> I'm trying to do the folliwing (without luck):
>
> I have a table with peoples names and their permanent addresses (lets call
> it [ADPERM]) and people's temporary addresses (lets call it [ADTEMP]). In
> the perm. address fiels there is always an address, but not always in the
> temp. address field. But, if there is something in [ADTEMP], I want to use
> that one instead of the permanent one.
>
> So, I'm trying to make a select query with a calculated field. In the first
> line ("fied") I have the following expression:
>
>      ADR: IF [ADTEMP] IS NULL THEN ADR=[ADPERM] ELSE ADR=[ADTEMP]
>
> Actually I've tried several versions of the previous, but the result is
> always the same: SYNTAX ERROR! Too bad...
>
> So, what am I doing wrong? Is it not allowed to use "if...then...else..."
> -statement?
>

I don't have Access here in front of me...have you tried to use IIF() instead
of the IF THEN ELSE construct. I'm not sure (never tried it) if you can use
the IF THEN ELSE in a query calculated field.

Good luck,


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Tue, 11 May 1993 10:11:59 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Calculated field in a select query & file sizes
In-Reply-To:  Message of Tue,
              11 May 1993 07:55:29 PDT from <[e-mail] L.COM>

If...Then...Else is a statement that is used in Access Basic only.  See
page 246 of the Language Reference.

The IIf() function can be used in either Access Basic or as the value of
a text box.  See page 248 of the Language Reference.  Syntax is

IIf(expr, truepart, falsepart)

where

expr    Expression you want to evaluate

truepart  Value or expression returned if expr is TRUE (-1)

falsepart Value or expression returned if expr is FALSE (0)


See also the Switch() function (page 462) if you need a similar function
that operates on variable expressions rather than true/false.

HTH, Nathan

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Tue, 11 May 1993 10:28:45 CST
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "John A. Olson" <[e-mail]>
Subject:      Re: Sorting in Reports

>Is there any way to sort records in a report in a way that I can change
>dynamically?
>Can I change the sort-options via Access Basic?

>To my opinion there should be a way to do this WITHOUT having rights to
>change a report, it should be possible to chnage sort-properties at
>run-time.

< stuff deleted>

Sure there is!  Don't worry, be happy! :)

Base your report on a query.  You can create queries on the fly using
Access Basic code which means you can use the same report over and over
by just changing the way that your query sorts things.  You have to keep
the name of your query the same, and have the same field names to match
what's in your report though.  If you are interested in how to create/
modify queries "on-the-fly" let me know and I'll send some samples I've
created.  Also, check the Introduction to Programming book which came with
ACCESS for a good explanation of how to modify an existing query using
Access Basic.

Good Luck! :)

John Olson
[e-mail]
Computing Devices International
a Division of Ceridian Corp. (f.k.a Control Data)
John A. Olson
Internet address:  [e-mail]
=========================================================================
Date:         Tue, 11 May 1993 15:19:02 -0400
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         David So <[e-mail]>
Subject:      ASSECC ODBC driver

Hi

The ODBC allows Access to communicate with SQLServer.

Can any other database system go with this new interface standard?

thanks/david
=========================================================================
Date:         Wed, 12 May 1993 11:39:26 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Con Zymaris <[e-mail]>
Organization: CSIRO, Div. Building Constr. and Eng'ing, Melb., Australia
Subject:      Re: ASSECC ODBC driver
In-Reply-To:  <[e-mail]>; from "David So"
              at May 11, 93 3:19 pm

According to David So:
>
> Hi
>
> The ODBC allows Access to communicate with SQLServer.
>
> Can any other database system go with this new interface standard?
>
> thanks/david
>
David,
M'Soft are trying to get everyone and their mother-in-law writing ODBC drivers
for their Database backends

--

_________________________________________________________ Nebulae for sale
| Con Zymaris                   Phone [phone]    |       *
| Programmer                    FAX  [phone]     |   *      *
| Cybersource Pty. Ltd.         PO BOX 171, Glenhuntly  |    *   *    *
|                               3163 Australia          |     *       *
| Internet: [e-mail]                      | *         *     *
|_______________________________________________________|  Enquire within...
=========================================================================
Date:         Tue, 11 May 1993 23:09:08 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Rob Cermak <[e-mail]>
Subject:      DDE conversation from VB/WIN Pro 2.0 to Microsoft Access 1.0

The subject covers what my goal is.  This is a detailed message of
what I have found out so far.  The only code that results to
anything comming back from MS-Access....

frm.Text1.LinkMode=0
frm.Text1.LinkTopic="Microsoft Access|System"
'A link topic of Access just does not work!
frm.Text1.LinkItem="SysItems"
frm.Text1.LinkMode=2            'Manual
frm.Text1.LinkRequest

Output to Text1(box):
        Status   Formats   SysItems  Topics

frm.Text1.LinkItem="Status"
Output:  Ready

frm.Text1.LinkItem="Formats"
Output:  Text  CSV

frm.Text1.LinkItem="Topics"  'With Access just booted (no open files)
Output:  System  UTILITY  WIZARD

'With Access opened with a TEMPLATE.DBF
Output:  System  UTILITY  WIZARD  TEMPLATE

'With Access opened with a TEMPLATE.DBF and the TABLE: (called OBS)
Output:  System  UTILITY  WIZARD  TEMPLATE  TEMPLATE  TEMPLATE

I would have thought that the OBS table would have been one of the
choices so that one could poke/send values into the table.  I also
have not figured out how to get Access to automatically open the
TEMPLATE & OBS files.  Does someone have some code that you could
share with me?  I'm in a bind.

** Please send E-mail to me directly ([e-mail])

Rob Cermak                              EMAIL : [e-mail]
Programmer NJ Climate Center &          USMAIL: Rutgers University
Prog/Tech Rutgers Meteorology-COOK              Department of Meteorology
FAX             :908 932-7922                   Cook College  PO BOX 231
Meteorology Dept:908 932-9387                   New Brunswick NJ 08903-0231
=========================================================================
Date:         Tue, 11 May 1993 22:14:40 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Tech notes

FINALLY Computing Services set up my filelist.  :)

The Microsoft Access Technical Notes and Supplemental Notes files are
now available via [e-mail].  These were downloaded from
the Microsoft Download Service about 3 weeks ago.

You can send the command IND ACCESS-L to [e-mail] for
a copy of the list of files.

For those not familiar with Listserv's file server commands, please
send the command INFO REFCARD to [e-mail] and read it.

Nathan Brindle
List Administrator

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Wed, 12 May 1993 12:15:32 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Pekka Koskinen CIMO <[e-mail]>
Subject:      Calculated field -problem

Hi folks!

Earlier this week I game up with a problem with a calculated field. I tried
to set it with "IF...THEN...ELSE..." -statement, but couldn't get it work.
Nathan Brindle asked me to use "IIF" -statementm, and it worked!
Thanks a lot, Nathan!

I understood that it's not allowed to use "IF...THEN...ELSE..." anywhere
else than Access-basic.

Pekka
=========================================================================
Date:         Wed, 12 May 1993 13:39:00 BST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Anne L Zorner R27.G5/" <[e-mail]>
Subject:      re ODBC drivers

SQL Support Section (SQS)         Mail [e-mail]
===============================================================
IBM's DB2/6000 product will come with one when the product is
relaesed in Jiuly.
Oracle are working on one but you will also need their *NET product.
Ingres are working on one but you will also need INGRES*NET.
Anne

Thankyou
===============================================================
=========================================================================
Date:         Wed, 12 May 1993 09:34:02 -0400
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Donn C Young <[e-mail]>
Subject:      Re: ASSECC ODBC driver
In-Reply-To:  <[e-mail]>

On Tue, 11 May 1993, David So wrote:

> The ODBC allows Access to communicate with SQLServer.
> Can any other database system go with this new interface standard?

As another note mentioned, everyone seems to be writing ODBC drivers for
their particular flavor of database. Our DEC person just dropped off a
field test version of DEC's ODBC driver for its Rdb database. This driver
will allow folks to import/attach Rdb files from a VAX to MSAccess on a
PC. The drivers will be part of Rdb version 5.1 to be released in July.
If you have an Rdb license, you can probably get the driver free. It
seems to work just fine. To use the driver, on your PC you need: Win 3.x,
an ODBC application like MSAccess, and DEC's Pathworks for DOS [either
the DECnet or TCP/IP version]. On the VAX server, you'll need VMS 5.3 or
later, Rdb 4.0 or later, DECnet or TCP/IP, and Pathworks. Installation
takes about 5 minutes. Apparently (I don't use this), if you have
RdbAccess, you can access DB2, ORACLE, or RMS databases as well using
this ODBC driver.

Call your local DEC folks if you'd like to try this front end to Rdb files.

Donn Young, Biostatistics Unit, OSU Cancer Center
[e-mail]
=========================================================================
Date:         Wed, 12 May 1993 16:54:02 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Tom Emerson <[e-mail]>
Subject:      Unsubscribe

Please remove me from the ACCESS-L list.

internet: [e-mail]
bitnet:   ictee@asuacad

Tom Emerson, KAET-TV Arizona State University  [phone]
=========================================================================
Date:         Wed, 12 May 1993 21:26:53 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bhanu MK <[e-mail]>
Organization: BARUCH College, CIS Department
Subject:      Re: file sizes
In-Reply-To:  Message of Tue, 11 May 1993 16:01:45 CET from <[e-mail]>

Hi there,

    Compressing would be great though... but watch out you may at times get
corrupted database after a compress if the database is fairly large.  I am
not quite sure if this is a bug... Best thing is make a backup of the uncompres
sed one just in case.  If the compressed one is bad.. you still are safe.

BMK
=========================================================================
Date:         Wed, 12 May 1993 22:27:49 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: file sizes

I've had the same corruption problem.  It appears to be liked to systems
running stacker.

Bill Stewart
Glendale Community College
=========================================================================
Date:         Thu, 13 May 1993 10:00:01 +0200
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Rory BROWNE @ILO - 822-4634" <[e-mail]>
Subject:      Tech Notes

IND ACCESS-L
=========================================================================
Date:         Thu, 13 May 1993 08:11:46 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Tech Notes
In-Reply-To:  Message of Thu,
              13 May 1993 10:00:01 +0200 from <[e-mail] .DEC.COM>

You send that command (IND ACCESS-L) to LISTSERV@INDYCMS, not to the list.

Nathan Brindle
List Administrator

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Thu, 13 May 1993 15:33:51 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: file sizes
In-Reply-To:  Message of Wed, 12 May 1993 22:27:49 -0700 from <STEWART@GC>

On Wed, 12 May 1993 22:27:49 -0700 Bill Stewart said:
>I've had the same corruption problem.  It appears to be liked to systems
>running stacker.
>
>Bill Stewart
>Glendale Community College

It's interesting to hear that someone else had trouble with Stacker!  I
lost a whole database (luckily I had it backed up) while I was using
Stacker, and about a week later I switched to MS-DOS 6 and DoubleDisk
and haven't had a bit of trouble since.  Stacker seemed to act quirky
at odd times, but yes, mostly when I was running Access.  I never really
made the connection before.

Nathan

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Thu, 13 May 1993 18:05:47 USM
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Victor Parada G." <[e-mail]>
Subject:      Secret screen of MS Access

Hi all!    Please take a break  ;-)

If I'm disturbing you, just ignore this post.

I never read about Access' secret screen in this list.
Almost all MS-Windows applications (including MS's) have
a window with a funny animation or picture that require
some secret codes or key-bindings to appear.

If this is new for you, just follow this instructions:
open File Manager, then keep pressed SHIFT and CONTROL
key while going to Help/About screen, doble-click over
the Windows icon and close it, without releasing the
keys, repeat the secuence.   A little animation begins.
Doing this another time shows another and more complex
(not at all) animation.   There are 4 variants of this,
representing some of the MS developers faces.
This works on any of the programs included in the Windows
setup disks.

Now, the question: Who knows how to get the Access' secret
screen?   If you know the answer, please wait while others
are trying to get it.

Have some fun...   Bye...   ++V
__
           | / . -/-           [e-mail]     Victor Parada G.
  -/- -/-  |/ /  / () ( ()     [e-mail]    Informatica UTFSM
=========================================================================
Date:         Thu, 13 May 1993 17:45:08 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: file sizes

Good to hear we reached a conclusion on the problem(maybe?).  I've herd
some problems about DOS 6 doublespace.  There seems to be times where files
are sometimes turned into garbage.  I've herd that MS is investigating the
cause.

-----------------------------
Bill Stewart
Glendale Community College
6000 W. Olive
Glendale Az. 85302
-----------------------------
=========================================================================
Date:         Fri, 14 May 1993 07:50:08 MDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     Converted from PROFS to RFC822 format by PUMP V2.1
From:         "Brian Keeler (403) - 471-8623" <[e-mail]>
Subject:      Re: file sizes
In-Reply-To:  note of 93-05-13 19:34

I too have experienced this, lost cluster, chains etc. and even lost the
whole compressed disk once, ( having a good backup process helps ). The real
big problem is CVF (compressed volume file) errors and whats causing them.
I actually quit using the MSBACKUP and went back to NORTONS proprietary
disk format backup as it appeared to me that everytime I used the MSBACKUP
and it updated the archive flag, I had problems after that. I agree that MS
has got to look into this, because I know of 5 other people that went to
DOS 6 and are all having similar problems!!

Brian Keeler (403) - 471-8623     ..What is a CD-ROM ??
Application Services Coordinator   3 billion pits arranged
Information Services Division      in a 3 mile spiral...
domain: [e-mail]
=========================================================================
Date:         Fri, 14 May 1993 18:44:54 BST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Anne L Zorner R27.G5/" <[e-mail]>
Subject:      re permissions

SQL Support Section (SQS)         Mail [e-mail]
===============================================================
If I assign a permission to a group and then assign a user to that
group should the user inherit the rights assigned to the group?
Anne

Thankyou
===============================================================
=========================================================================
Date:         Fri, 14 May 1993 18:36:50 BST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Anne L Zorner R27.G5/" <[e-mail]>
Subject:      Re Access Security

SQL Support Section (SQS)         Mail [e-mail]
===============================================================
How many of you have created secure databases on networks?

How did you set access up to run... with full installation on each
users PC or with full installation just on the server and minimum
installation on each PC?

With the former method what did you do about each users version
of the SYSTEM.MDA?

Anne

Thankyou
===============================================================
=========================================================================
Date:         Sat, 15 May 1993 12:00:05 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sat, 15 May 1993 12:00:05 EST
=========================================================================
Date:         Sat, 15 May 1993 12:00:12 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sat, 15 May 1993 12:00:12 EST
=========================================================================
Date:         Sat, 15 May 1993 12:00:51 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sat, 15 May 1993 12:00:51 EST
=========================================================================
Date:         Sun, 16 May 1993 11:48:28 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sun, 16 May 1993 11:48:28 EST
=========================================================================
Date:         Sun, 16 May 1993 11:48:31 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sun, 16 May 1993 11:48:31 EST
=========================================================================
Date:         Sun, 16 May 1993 11:49:44 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sun, 16 May 1993 11:49:44 EST
=========================================================================
Date:         Sun, 16 May 1993 11:49:59 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sun, 16 May 1993 11:49:59 EST
=========================================================================
Date:         Sun, 16 May 1993 12:05:08 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sun, 16 May 1993 12:05:08 EST
=========================================================================
Date:         Sun, 16 May 1993 12:05:09 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sun, 16 May 1993 12:05:09 EST
=========================================================================
Date:         Sun, 16 May 1993 12:05:30 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Sun, 16 May 1993 12:05:30 EST
=========================================================================
Date:         Sun, 16 May 1993 13:01:28 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Hal Stitt <[e-mail]>
Subject:      Re: Service Message

I have received this message about 15 times. I haven't sent a message to
the address in the report. Please check to see who should be getting this.
Hal Stitt
=========================================================================
Date:         Sun, 16 May 1993 18:04:47 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Service Message
In-Reply-To:  Message of Sun,
              16 May 1993 13:01:28 -0700 from <halstitt@NETCOM.C OM>

Regarding the service messages from POSTMASTER@INDYCMS--I will have to
check into why that's happening.  Sorry for the inconvenience, but this
is an error I've never seen before.  Please bear with it...I don't think
it's anything users have done, but a misdirected error message that should
have come to my error account rather than to the list.

Nathan Brindle
ACCESS-L List Administrator

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Mon, 17 May 1993 11:29:12 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Con Zymaris <[e-mail]>
Organization: CSIRO, Div. Building Constr. and Eng'ing, Melb., Australia
Subject:      Re: file sizes
In-Reply-To:  <[e-mail]>; from "Nathan
              Brindle" at May 13, 93 3:33 pm

According to Nathan Brindle:
>
> On Wed, 12 May 1993 22:27:49 -0700 Bill Stewart said:
> >I've had the same corruption problem.  It appears to be liked to systems
> >running stacker.
> >
> >Bill Stewart
> >Glendale Community College
>
> It's interesting to hear that someone else had trouble with Stacker!  I
> lost a whole database (luckily I had it backed up) while I was using
> Stacker, and about a week later I switched to MS-DOS 6 and DoubleDisk
> and haven't had a bit of trouble since.  Stacker seemed to act quirky
> at odd times, but yes, mostly when I was running Access.  I never really
> made the connection before.
>
I lost a whole partition with Superstore, while running Access. Disk light
stayed on, machine re-boot, 100 Meg lost. Dreadfull sight.

--

_________________________________________________________ Nebulae for sale
| Con Zymaris                   Phone [phone]    |       *
| Programmer                    FAX  [phone]     |   *      *
| Cybersource Pty. Ltd.         PO BOX 171, Glenhuntly  |    *   *    *
|                               3163 Australia          |     *       *
| Internet: [e-mail]                      | *         *     *
|_______________________________________________________|  Enquire within...
=========================================================================
Date:         Mon, 17 May 1993 01:53:49 -0500
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Piotr Karocki <[e-mail]>
Subject:      Help! Access add tables to my database!

Please, help!
I 'm creating database. Suddenly system crashed.
When I run Access again, I have 6 additional tables in database:
MSysACEs, MSysColumns, MSysIndexes, MSysMacros, MSysObjects, MSysQueries.
I tried to 'repair database', but this tables remain in database.
I cannot delete its (first, I cannot rights to do it, even on single
computer, but rights I 'granted' to myself) - I receive message box:
'cannot delete - table locked'.

So: what I have to do to delete this 6 tables?

--
Piotr Karocki,
student of Computer Science,
Jagiellonian University,
Cracow, Poland
=========================================================================
Date:         Mon, 17 May 1993 09:15:08 CET
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Hilger Martin Dr." <[e-mail]>
Subject:      Re: Re Access Security

Hi Anne et al,

Right now we are programming on a NetWare 3.11 network. We just put the
SYSTEM.MDA-path to a directory that has the same mapping for all clients.

What I can't say is how much performance it costs to have more than one
user using the database. But the system IS much slower than my local
system.

It seems to be possible to avoid Access's security system by simply putting
another path to another SYSTEM.MDA into the .INI.

This SURE is a big lack of security!

Martin
=========================================================================
Date:         Mon, 17 May 1993 22:57:14 -0500
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "JULIAN BOOT, UNIVERSITY BOOKSHOP" <[e-mail]>
Subject:      Re: file sizes

I have been reading with some interest the tales of woe relating to
data compression software and the aparent stability of MS's new product
bundled with DOS 6.

I have had in the past problems with SuperStor and DoubleDensity (from Abacus)
and looked at Stacker before deciding to purchase a second hard disk.  Problems
usally resticted themselves to programs not running or false "fatal error"
reports - occasionally I would lose the odd file, but this happens with a non-c
compressed FAT disk anyway.

My question is this.  Does anybody actually *know* what Access is doing to
 causethese problems?  One possible answer I have heard is MS programmers have
 been
using some tricks Stacker does not know about in an attempt to get people
who need datacompression, but not a new DOS, to upgrade anyway.  This does seem
a tad scynical, however.

Julian Boot
Computer Science
University of Queensland
Brisbane, Australia
Internet:  [e-mail]
=========================================================================
Date:         Mon, 17 May 1993 08:35:11 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: file sizes
In-Reply-To:  Message of Mon,
              17 May 1993 11:29:12 EST from <[e-mail] IRO.AU>

As it turns out, when I went home Friday night after making that statement
about DOS 6.0 and DoubleDisk, I turned the machine on and my 84MB SCSI
drive ran about 5 minutes and crashed....

DOS 6.0 is currently suspect, because I can still get the drive to boot
if I wait long enough, but as soon as I try to do something that involves
the disk (other than take a directory), it freezes up tight.  And I only
suspect DOS because I was having little "epileptic" episodes like this
with this drive under 5.0 also.  But those were resolvable by shutting
the machine off and waiting a while.

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Mon, 17 May 1993 08:59:54 MDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     Converted from PROFS to RFC822 format by PUMP V2.1
From:         "Brian Keeler (403) - 471-8623" <[e-mail]>
Subject:      CVF errors, lost chains/clusters

Subject: CVF errors, lost clusters/chains etc.

I have been experiencing lost cluster, chains etc. and even lost the
whole compressed disk once, ( having a good backup process helps ).
The real big problem is CVF (compressed volume file) errors and whats
causing them.
I actually quit using the MSBACKUP and went back to NORTONS
proprietary disk format backup as it appeared to me that everytime
I used the MSBACKUP and it updated the archive flag, I had problems
after that. I think that MS has got to look into this, because I
know of 5 other people that went to DOS 6 and are all having similar
problems!! This has not effected any of my files running my CD yet.
Running a 486/33, 8 megs, 200 meg hard drive, Panasonic CD, ATI sound
card, windows 3.1 and DOS 6.0 with dblspace.
I am wondering if anyone else has experienced similar problems after
upgrading to DOS 6, because at DOS 5 everything was great.

Brian Keeler (403) - 471-8623     ..What is a CD-ROM ??
Application Services Coordinator   3 billion pits arranged
Information Services Division      in a 3 mile spiral...
domain: [e-mail]
=========================================================================
Date:         Mon, 17 May 1993 08:18:53 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Brian Henning <[e-mail]>
Subject:      Re: Help! Access add tables to my database!

> Please, help!
> I 'm creating database. Suddenly system crashed.
> When I run Access again, I have 6 additional tables in database:
> MSysACEs, MSysColumns, MSysIndexes, MSysMacros, MSysObjects, MSysQueries.
> I tried to 'repair database', but this tables remain in database.
> I cannot delete its (first, I cannot rights to do it, even on single
> computer, but rights I 'granted' to myself) - I receive message box:
> 'cannot delete - table locked'.

> So: what I have to do to delete this 6 tables?


You don't want to delete them, they are system files. Just pick the View Menu,
then Options and change the setting that says something like "Hide System
Objects" I'm not on a machine with Access at the moment so I can't give you the
exact verbage.

Brian Henning
U of AZ
=========================================================================
Date:         Mon, 17 May 1993 10:16:45 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: CVF errors, lost chains/clusters
In-Reply-To:  Message of Mon, 17 May 1993 08:59:54 MDT from <[e-mail]>

I was told by a colleague this weekend to read Info World (he just said
it was a recent issue) for an article about DOS 6.0 problems.  One of
them that he remembered off the top of his head was something about
being sure you don't stuff the whole CVF full, and another one was
something about disabling the defragmenter when you run DoubleDisk the
first time.  I have not seen the article but those were two of the things
he cited when we were talking about my hard drive (RIP).

When I install my <new> drive this week (200MB IDE), I will NOT be using
the compression software.  This is more because I won't need it than because
I think it's to blame for my problems...but I'm still wavering on placing
the blame.  :)  DOS 6 has got some really nice new features, and I hope
I'll be able to continue using it.

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Mon, 17 May 1993 23:39:32 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "C.S. Lim" <[e-mail]>
Subject:      ACCESS REPORTED BUGS!
In-Reply-To:  <[e-mail]>; from "JULIAN BOOT,
              UNIVERSITY BOOKSHOP" at May 17, 93 10:57:14 pm

I'd read this articles from newsgroup comp.database .

As there might be someone with no access to Compu$erve or newsgroup,
I distribute it to the list.


The following was posted by Microsoft on Compu$erve:


The following list identifies problems that may occur when using Microsoft
Access.  This list contains all significant, reproducible problems that we
have found since releasing the product.  The list includes bugs that could
potentially cause a General Protection Fault in Access or in some other
way might cause significant difficulty for many users, but it does not
include all known problems to date.  The list will be updated as new
problems are identified and validated.  A detailed description of each
problem and the suggested work around is also provided below. (4/20/93)

1.  Incorrect Windows For Workgroups driver can cause file truncation
    (correct driver included with Microsoft Access)
2.  Incorrect LAN Manager driver can cause file truncation (correct
    driver included with Microsoft Access)
3.  Microsoft Access SETUP may have problems with DOS APPEND statement
    in Autoexec.bat
4.  ATI Ultra video driver not compatible with Microsoft Access
5.  Microsoft Access SETUP may leave temporary directory and files on
    disk
6.  Problem importing .DBF files where record length exceeds dBASE
    maximum
7.  Microsoft Access cannot use Btrieve data with indexes across column
    boundaries
8.  Fixed Width Import does not correctly translate extended characters
9.  Cannot hide modal/popup forms with the OpenForm action
10. Form dynaset references do not always work when using form variables
11. Problem using Running Sum property with control that evaluates to
    #ERROR
12. Beta versions of ODBC drivers will not work with Microsoft Access
13. STACKER 3.0 incorrectly reports that database files are corrupted
14. Cannot use the CVDate and IsDate functions with empty string argument
15. Cannot declare new form object variable during break mode
16. Cannot attach to foreign database in multiuser environment
17. Using LIKE with trailing spaces and wild cards will not work properly
18. Query with descending sort on indexed duplicate data can return
    incorrect results
19. Cannot add counter columns to existing tables with large amounts of
    data
20. Fixed Width Import does not work with variable length records
21. Searching on Paradox data with multi-column indexes that contain
    NULLS
22. Update Queries do not work with "Restrict Available Fields" Option
    disabled
23. Using the BTRIEVE NLM may give an undefined error alert
24. Duplicate values may be returned on "Unique Values Only" queries
    (DISTINCT)
25. Microsoft Access may have problems when multiple instances of
    extremely large query definitions are used
26. Programmatically hiding a control in the footer of a form that is
    viewed in datasheet mode may cause problems
27. Using the ListParameters method on a database object does not
    generate an error as expected
28. Problems Importing Lotus 1-2-3 spreadsheets with extremely large
    numbers of formatted cells
29. Adding fields to a table in multiuser mode may cause fields to
    become cross-linked
30. Property sheet and toolbox may show up in form browse mode
31. Entering an invalid IIf() in a ControlSource on a form may cause a
    General Protection Fault
32. Problem when CanGrow property set to Yes on controls in subreports
33. Printing a report with a subreport created from a form with a
    DefaultView of Datasheet causes problems


1. Incorrect Windows For Workgroups driver can cause file truncation
(correct driver included with Microsoft Access)

NOTE:  This problem was discovered before Microsoft Access was released
and all copies of Microsoft Access include the updated Windows for
Workgroups driver and installation instructions.

DESCRIPTION:  If you have an early version of the Windows for Workgroups
WFWNET.DRV file (before 11-02-92), using the Network button in Access
dialog boxes to connect to password-protected servers may cause any
database files that you open on that server to become truncated.

WORK AROUND:  Update the WFWNET.DRV driver file using the driver update
program included with Microsoft Access.  Complete instructions are
contained in the flier included in your copy of Microsoft Access.


2. Incorrect LAN Manager driver can cause file truncation (correct driver
included with Microsoft Access)

NOTE:  This problem was discovered before Microsoft Access was released
and all copies of Microsoft Access include the updated LAN Manager driver
and installation instructions.

DESCRIPTION:  Using Microsoft Access on a Microsoft LAN Manager
workstation (prior to version 2.2) can cause files to become truncated.
Products that may be affected include: Microsoft LAN Manager prior to
version 2.2; DEC Pathworks for DOS version 4.1;
NCR StarGroup LAN Manager version 3.6; Olivetti Olinet LAN Manager version
2.1; Ungermann-Bass LAN Manager version 2.1.

Database truncation is most likely to occur when a user workstation
operates faster than the file server on which the database file is stored.
(Note that the CPU speed alone does not determine the operation speed of
the server. Heavy network traffic can make the server operate more slowly
than a user workstation(s).)

WORK AROUND:  If you have LAN Manager 2.1 or 2.1a, install the LAN Manager
Hotfix included with Microsoft Access appropriate to your version of LAN
Manager.  If you have LAN Manager 2.0, include the appropriate line in
your LANMAN.INI file for LAN Manager versions prior to 2.1.  Refer to the
instructions included in the README.TXT file in your Microsoft Access
package for complete details.


3. Microsoft Access SETUP may have problems with DOS APPEND statement in
Autoexec.bat

DESCRIPTION:  If you have an APPEND statement in your AUTOEXEC.BAT file
and that APPEND statement defines a path where other README.TXT files
exist, Microsoft Access SETUP may abort when installing the README.TXT
file.

WORK AROUND:  Remove or remark out the APPEND statement in your
AUTOEXEC.BAT file and reboot your computer before trying to setup
Microsoft Access.


4. ATI Ultra video driver not compatible with Microsoft Access

NOTE:  Use GO ATITECH to acquire the newest versions of ATI drivers.
Newer versions may correct some or all of the problems reported.

DESCRIPTION:  Using ATI-supplied drivers included with the ATI Ultra video
card can cause any of the following problems in Microsoft Access: 1)
General Protection Fault on disabled cascading menus (most common case is
Layout menu with Align command disabled in form or report design); 2)
disabled buttons not visible; and 3) text alignment problems.

WORK AROUND:  The suggested work around for these problems is to use the
8514 video drivers included with Windows 3.1 and not the video drivers
supplied with the ATI Ultra video card.  NOTE: Microsoft is working with
ATI on this problem.  We will post more information on this forum as it
becomes available.


5. Microsoft Access SETUP may leave temporary directory and files on disk

DESCRIPTION:  If you request SETUP to install SHARE and then choose the
option to reboot your machine at the end of the installation process,
SETUP will not properly clean up temporary files on your hard disk.  This
leftover directory will have the name MS-SETUP.T and will contain data
files totaling approximately 600K.  Besides taking up hard disk space,
these files will have no affect on Microsoft Access or any other
applications.

WORK AROUND:  Do not choose to reboot your machine at the end of the
installation process or simply delete the files and directory after the
reboot process.


6. Problem importing .DBF files where record length exceeds dBASE maximum

DESCRIPTION:  CodeBase++ v1.07 allows you to create .DBF files where the
record length exceeds the dBASE IV maximum.  Microsoft Access may hang
when trying to import these type of .DBF files.

WORK AROUND:  Export the CodeBase++ .DBF file to delimited text, then
import the ASCII file into Microsoft Access.


7. Microsoft Access cannot use Btrieve data with indexes across column
boundaries

DESCRIPTION:  Microsoft Access will display the error message: "File is
corrupt or isn't an Access file" when attempting to attach or import a
BTRIEVE file which has an index defined across a column boundary.

Access does not support BTRIEVE indexes which have keys defined on a
partial column or across column boundaries.  Indexes which have a segment
of the key which is defined to cross a column boundary are not supported
by the Xtrieve data dictionary format.  Xtrieve may ignore these indexes
and import the file correctly but Microsoft Access does not.

WORK AROUND:  You must remove the indexes or recreate them so that they
align on column boundaries.


8. Fixed Width Import does not correctly translate extended characters

DESCRIPTION:  When importing a Fixed Width ASCII file, Microsoft Access
does not properly translate extended characters from OEM to ANSI
representation.  The first 4K of data is imported and translated
correctly, but all data after the initial 4K will not translate correctly.

WORK AROUND:  Convert the ASCII file from OEM to ANSI using another
Windows application, such as Windows Write.  Using Windows Write, simply
open the file, responding 'Yes' to the convert alert, then save the file.


9. Cannot hide modal/popup forms with the OpenForm action

DESCRIPTION:  Using the OpenForm action to hide a modal/popup form may
cause a General Protection Fault.

WORK AROUND:  Hide a modal/popup form by using the SetValue action to set
the forms .Visible property to False.


10. Form dynaset references do not always work when using form variables

DESCRIPTION:  If you reference a form dynaset with variables, you may
receive a General Protection Fault.

WORK AROUND:  Always refer to a form dynaset with explicit references
through the form.  The first code fragment below shows how to references a
form dynaset safely and the second code fragments shows what will most
likely cause the problem.

A)     SAFE:
       forms!testform.dynaset!col1="foo"

B)     MAY CAUSE PROBLEMS:
       dim f as form
       set f = form!testform
       f.dynaset!col1 = "foo"


11. Problem using Running Sum property with control that evaluates to
#ERROR

DESCRIPTION:  If a report contains a control where the Running Sum
property is set to 'Over Group' or 'Over All' and the control evaluates to
#ERROR, Microsoft Access will cause a General Protection Fault.

WORK AROUND:  Correct the expression in the control source property so
that it evaluates correctly.


12. Beta versions of ODBC drivers will not work with Microsoft Access

DESCRIPTION:  When using Beta versions of the ODBC drivers, Microsoft
Access may experience General Protection Faults in ODBC.DLL.  The problem
is that when Microsoft Access initiates an ODBC connection, ODBC does not
properly check the version of the ODBC driver.

WORK AROUND:  Rename or delete the beta version of ODBC.DLL and run the
ODBC setup program from the setup disks that come with Microsoft Access.
This will install a current ODBC.DLL file.


13. STACKER 3.0 incorrectly reports that database files are corrupted

DESCRIPTION:  Running Stacker's "check /=D /F" command will often report
that some Access .mdb files are corrupt and should be deleted.  The
problem is that the "/=D /F" flags are for development and debugging
purposes and will report things which are really not problems.  If for
some reason you run CHECK.EXE with the /=D switch and it asks if you want
to delete a file, answer NO!  The file is fine.  These are superfluous
error messages.

WORK AROUND:  Do not run CHECK.EXE with the /=D switch.  If you do run
CHECK /=D, answer NO when prompted to delete files.  Stac Electronics has
written a document explaining the "Lost Sector Groups" reported by CHECK
/=D.  The document is referenced as TEC042.DOC on CompuServe or the Stac
BBS and as document #3003 on STAC FAX, Stac Electronics' automated FAX
response service.


14. Cannot use the CVDate and IsDate functions with empty string argument

DESCRIPTION:  The CVDate function is used to convert a string or numeric
expression to a variant of type date.  If this function is called with the
empty string as the expression (i.e. CVDate("")) then you will get a
general protection fault.  The IsDate function has the same problem.

WORK AROUND:  Verify that you are passing valid date strings in the
argument to CVDate.


15. Cannot declare new form object variable during break mode

DESCRIPTION:  The General Protection Fault occurs when declaring an object
variable (form, table, etc.) during break mode (when debugging Access
Basic code) and then trying to recompile the code.  The following are
examples of object variable declarations:

  Dim F as Form
  Dim T as Table

WORK AROUND:  Don't add these type of variables while in break mode.


16. Cannot attach to foreign database in multiuser environment

DESCRIPTION:  Attaching/importing will only work if you can open the
foreign database file (dBASE, Paradox, BTRIEVE, etc.) exclusively.  If you
attempt to attach to these types of files while others are using them you
will get an error message stating that the table or file is already in
use.  This problem is isolated to attach and import.  Once you have
successfully attached to a file of this type you can then edit or browse
this file in a multiuser environment.

WORK AROUND:  Must obtain exclusive access to foreign database file in
order to import or attach.


17. Using LIKE with trailing spaces and wild cards will not work properly

DESCRIPTION:  When using the LIKE operator with trailing spaces and
trailing wild cards (i.e. LIKE "The *") you will not always get back the
proper results.  Access ends up trimming the trailing spaces in this case
and actually performs LIKE "The*".  This is only a problem when you have
both trailing spaces and the trailing wild card character.

WORK AROUND:  A sample work around for the LIKE "The *" example would be
as follows:

     (LIKE "The*" AND (mid$([Field],4,1) = " "))


18. Query with descending sort on indexed duplicate data can return
incorrect results

DESCRIPTION:  When sorting data in descending order on a column that is
indexed and contains over 506 duplicate entries, Access can return
incorrect results to the user (wrong number of rows).  This can occur when
the Index property for a column is set to Yes (No Duplicates) or Yes
(Duplicates OK), but not when there is a primary key on the column.
Non-primary key indexes can have multiple NULL entries.

WORK AROUND:  Remove the index from the column that is being sorted.  This
will cause the query to execute more slowly but will give you the correct
results.


19. Cannot add counter columns to existing tables with large amounts of
data

DESCRIPTION:  You cannot add counter columns to an existing table that
contains large amounts of data (roughly anything greater than 4 MB of
data).  This problem occurs because of a current limitation in the Access
transaction model (transaction size limited to 4 MB).  This problem
manifests itself with counter columns because the table data for this
column is updated as the column is added.  This update will take place
within a transaction and on large tables it will encounter the Access
transaction size limit.  The transaction will then rollback and the
counter column will not be successfully added.

WORK AROUND:  Follow these steps to add a counter column to a large
table:

  1) Copy/Paste the table structure (not the data) to a new table
  2) Add a counter column to this new table
  3) Create an append query that transfers data from the
     old table into the new table
  4) Verify new table has correct data
  5) Delete the old table
  6) Rename the new table to the name of the old table


20. Fixed Width Import does not work with variable length records

DESCRIPTION:  The fixed width import utility currently expects all records
in your text file to be the same length.  This most commonly presents
itself as a problem when the right most column of your text file has
strings of different lengths and they are not padded with spaces.  In this
case, Access will not import the data as you might expect (Access will
look to the next line for more characters if the right most column is not
properly padded).

WORK AROUND:  When importing ASCII Fixed Width files you must ensure that
all record (lines of text) are the same length.  In some cases this may
require that you manually or programmatically pad some lines with the
correct amount of spaces.  The following piece of code below is an example
of how one might programatically pad the lines of a text file so that all
lines (records) of the file are fixed length.

'----------------------------------------------------------------
'InFile$  - name of Fixed Width Ascii data file
'OutFile$ - name of new file to create with proper padding
'RecLen%  - Fixed length of each record in the padded file
'----------------------------------------------------------------
Sub PadFixedWidthFile (InFile$, OutFile$, RecLen%)

  fh1% = FreeFile
  Open InFile$ For Input As #fh1%

  fh2% = FreeFile
  Open OutFile$ For Output As #fh2%

  'Pad data and place in new file
  While Not EOF(fh1%)
    Line Input #fh1%, Ln$
    If (Len(Ln$) < RecLen%) Then
      Ln$ = Ln$ + String$(RecLen% - Len(Ln$), " ")
    Else
      MsgBox "Padding process aborted! - Data exceeds record length "
      MsgBox Ln$
      GoTo ExitPadFixedWidthFile
    End If
    Print #fh2%, Ln$
  Wend

ExitPadFixedWidthFile:
  Close #fh1%
  Close #fh2%

End Sub


21. Searching on Paradox data with multi-column indexes that contain NULLS

DESCRIPTION:  Using the Edit Find dialog to search Paradox fields for
specific values will not work properly if the field being searched is part
of a multi-column index, the field contains NULLS, and the "Search Fields
As Formatted" option is disabled in the EditFind dialog.

WORK AROUND:  The work around is to check the 'Search Fields as Formatted'
option so that the index is not used in the search.  Similarly, when
querying on Paradox fields that are part of a multi-column index and
contain NULLS you should use the LIKE operator in places where you might
normally use the equivalence operator.

AVOID:
   SELECT *
   FROM TestTable
   WHERE ((FieldX=23));

WORK AROUND:
   SELECT *
   FROM TestTable
   WHERE ((FieldX Like 23));


22. Update Queries do not work with "Restrict Available Fields" Option
disabled

DESCRIPTION:  If you use the View Options dialog to set the Query Design
option "Restrict Available Fields" to NO (the default is YES) then UPDATE
queries will not work correctly.  In the most common case Access will
cause a General Protection Fault, but there have been isolated cases where
the query actually executed to completion and incorrectly altered the data
in your table (the wrong columns get updated).

WORK AROUND:  Use the Query Properties dialog to set the "Restrict
Available Fields" option to No on a query by query basis when this
functionality is desired. Do not use the View Options
dialog to set this option on a global basis.


23. Using the BTRIEVE NLM may give an undefined error alert

DESCRIPTION:  Users who do not have all of the correct versions of
BREQUEST.EXE, WBTRCALL.DLL, and WBTRVRES.DLL may receive an "Internal
Database Error (-5001)" alert when using the BTRIEVE NLM.

WORK AROUND:  In order to get the BTRIEVE NLM to function properly, we
recommend that the NLM requester (client) uses the 6.0 versions of
BREQUEST.EXE, WBTRCALL.DLL, WBTRVRES.DLL and the 5.15 version of
BTRIEVE.NLM.  Follow these steps:

  1) Sign on to CompuServe.
  2) Go NOVLIB
  3) Go into the BTRIEVE/XQL library section.
  4) Download the BT515.ZIP file
  5) Use PKUNZIP.EXE to unpack the file.
  6) Unpack the BTRREQ.ZIP file that gets unpacked from step 5.
  7) Obtain the following files:
      WBTRCALL.DLL
      WBTRVRES.DLL
      BREQUEST.EXE
  8) Follow the readme notes to properly install and execute these files.
  9) The readme should also explain how to apply patches 1-65 to the
     BTRIEVE.NLM file on the server.

The WIN.INI file should also be modified with the following lines:

[BREQUESTDPMI]
datalength=4096
tasks=10
local=no
chkparms=no


24. Duplicate values may be returned on "Unique Values Only" queries
(DISTINCT)

DESCRIPTION:  DISTINCT queries may return a few duplicate values at the
beginning of the result set if the data set is very large.  This happens
only if the result set of the query is greater than 64K (counting the
duplicate values).  Record position of the duplicate values in the result
set is a contributing factor.

The conditions that must be met are as follows:

a) The underlying table(s) contains a large number of records (the result
   set must be >64K).
b) The data values that sort to the beginning of the output must have
   many duplicate values scattered throughout the input.

This can manifest itself in a Select query with the Unique Values Only
property turned on (DISTINCT).  It can also show up in a Crosstab query as
duplicated columns with names like "Field0", "Field1", etc.

This problem only occurs with Select DISTINCT queries, and not with the
much more common Select DISTINCTROW queries.

WORK AROUND:  For Select queries, use Totals with GROUP BYs instead of
using the Unique Values Only property.

For crosstab queries, use Fixed Column Heading to prevent the problem.


25. Microsoft Access may have problems when multiple instances of
extremely large query definitions are used

DESCRIPTION:  Trying to open more than one instance of a query may cause a
General Protection Fault in Microsoft Access when the query definition is
extremely large.  For example, if you have a form based on a query with a
query definition size of >32K and you then attempt to create a SnapShot
from the same query, Microsoft Access may cause a General Protection
Fault.  This happens because multiple versions of the query definition
must be saved, and the saved query definitions do not fit within the
query's segment space (the space allocated to each query).

Note: The number of records in the result set is NOT a contributing factor.

WORK AROUND:  Create a second query based on the first query and use one
of the queries for the form, and the other query for the SnapShot.


26. Programmatically hiding a control in the footer of a form that is
viewed in datasheet mode may cause problems

DESCRIPTION:  If you have a control in the footer of a form, you hide that
control in an event such as OnCurrent, and you then view the form in
datasheet view; Microsoft Access may cause a General Protection Fault.  In
datasheet view, Microsoft Access incorrectly assumes that there is a grid
column associated with the field being hidden; however, that is not true
in this case since the control is in the form's footer.

WORK AROUND:  Since forms with controls in the footer are normally meant
to be used in Form view, set the ViewsAllowed property for the form to
Form so that the form cannot be switched into datasheet view.


27. Using the ListParameters method on a database object does not generate
an error as expected

DESCRIPTION:  Attempting to list parameters for a database object is
illegal, but does not generate the expected compile-time error.  Instead,
it may cause a General Protection Fault in Microsoft Access.  For example,
the following subroutine causes a General Protection Fault even though it
should generate a compile-time error.

Sub Test
   Dim db As Database
   Dim Snap As Snapshot

   Set db = CurrentDB()
   Set Snap = db.ListParameters()
End Sub

WORK AROUND:  Check Microsoft Access Help or the Microsoft Access
"Language Reference" for the list of valid database object methods.


28. Problems Importing Lotus 1-2-3 spreadsheets with extremely large
numbers of formatted cells

DESCRIPTION:  The Lotus 1-2-3 spreadsheet import in Microsoft Access is
limited to 64,000 formatted cells.  All Lotus 1-2-3 cells are formatted.
Those not explicitly set by the user carry the general format.  If a Lotus
1-2-3 spreadsheet has more than 64,000 cells, then Microsoft Access cannot
import it and the system may hang during the import.

WORK AROUND:  To import Lotus 1-2-3 spreadsheets with greater than 64,000
cells, they must first be physically split into separate spreadsheets
where the number of cells in each does not exceed 64,000.  Importing
sub-ranges from these large spreadsheets does not eliminate the problem.


29. Adding fields to a table in multiuser mode may cause fields to become
cross-linked

DESCRIPTION:  In multiuser mode, adding a field to an existing table may
cause the new field to become cross-linked with another field already in
the table.  This can happen if more than one user accesses a table in a
very short space of time (within a couple of minutes of each other) and
the design of the table is modified at that time.  Information about open
tables is read from the system tables and cached by Microsoft Access.
This can mean that the information in the cache for one person is out of
date when that person makes a design change to a table that another person
has just used.  If so, the table may become corrupted.

The following example illustrates how you might cause this problem. User1
opens a table, and then closes it.  User2 then makes a quick design change
to the table and closes it.  User1 then reopens the table in design view
and makes another change.  If User1 still has the information for that
table cached, the system tables are not read again, so the table may
become corrupted.  It is not necessary for the same table to be opened by
both users.  The information on the table opened by User1 may be on the
same page in the system table as the information on the table modified by
User2 and if that page is cached by Microsoft Access then this problem can
occur.  This can be confusing to the users since they do not appear to be
using the same table.

Information in the cache is discarded on a regular basis for tables that
are not being used, so the problem will not occur unless the changes are
made before Microsoft Access has a chance to flush the cache.  To ensure
that the information in the cache is flushed, wait at least a minute
before opening a table in design.

When this problem occurs, it can manifest itself in one of the following
ways:

a) The data from another field in the table may be displayed in the new
   field.
b) Data typed into the linked field may be displayed in the new field.
c) Attempting to copy the table with the new field may generate a error.

WORK AROUND:  To correct this problem, simply compact the affected
database.  This is done by selecting Compact Database from the File menu
when no database is open.


30. Property sheet and toolbox may show up in form browse mode

DESCRIPTION:  Programmatically changing a form in form design mode may
cause Microsoft Access to display the property sheet and toolbox in browse
mode and could potentially lead to a General Protection Fault.  This will
only happen under all the following conditions:

1) It must be the very first time a form is opened in design mode after
   loading Microsoft Access.
2) The form must be opened in a restored or maximized state (not
   iconized).
3) There must be NO other MDI windows open (visible and enabled).  MDI
   stands for Multiple Document Interface.  In Microsoft Access, all open
   documents as well as the database container window use MDI windows.

WORK AROUND:  One of the following work arounds will ensure that this
problem is not encountered.

1) Open the design form as an icon (this is one of the arguments to the
   OpenForm action) and do not hide the DBC until after the form is
   opened.
2) Do not close the form before going to form browse mode.  The OpenForm
   action will switch a form from design mode to browse mode if the form
   is already open when the action is called.


31. Entering an invalid IIf() in a ControlSource on a form may cause a
General Protection Fault

DESCRIPTION:  If you use the IIf() function in a ControlSource property on
a form and you do not provide the necessary parentheses around the
parameter list, Microsoft Access may cause a General Protection Fault
instead of returning an error.  For example, the  following syntax is
incorrect and will cause a problem.

   =IIf IsNull([Fld]),"NULL","NOT NULL"

WORK AROUND:  Ensure that all IIf() functions include the required
parentheses on the parameter list.  The following syntax is a corrected
version of the one displayed above.

   =IIf(IsNull([Fld]),"NULL","NOT NULL")


32. Problem when CanGrow property set to Yes on controls in subreports

DESCRIPTION:  If a control in the subreport uses an expression or an
aggregate and has the CanGrow property set to Yes, Microsoft Access does
not calculate the value of the field correctly.  For example, assuming
your database contains the following table;

     Col
    =========
    Mickey
    Donald

If you create a subreport with a single textbox (Field1) that contains the
expression

    =IIf(IsNull([Col]),Null,[Col])

and you set the CanGrow property to Yes for Field1 and then embed that
subreport in another report, you will see the following displayed when you
print preview the report.

   Mickey
   Mickey

Note:  If the calculated subreport field contains an aggregate it displays
incorrect numeric values.

WORK AROUND:  Make sure that the CanGrow property on calculated fields in
subreports is set to No.


33. Printing a report with a subreport created from a form with a
DefaultView of Datasheet causes problems

DESCRIPTION:  Reports do not have a datasheet view, but forms created with
a default view of Datasheet can be saved as reports, which causes problems
in Microsoft Access.  If a report is created using SaveAsReport on a form
whose DefaultView property is set to Datasheet, and that report is
embedded in another report (subreport), Microsoft Access will cause a
General Protection Fault when the report is previewed or printed.

This can only happen when the subreport is created using the SaveAsReport
option from the form design File menu.

WORK AROUND:  When using the SaveAsReport option to create a report from a
form, be sure the DefaultView property of the form is NOT set to Datasheet.


Cal


    \_\_\_\_          \_         \_
    \_               \_  \_        \_
    \_               \_     \_       \_
     \_               \_\_\_\_\_       \_
      \_               \_       \_       \_
         \_\_\_\_\_     \_        \_       \_\_\_\_\_

Have a good day..
   Greeting from down under... *smile*
=========================================================================
Date:         Mon, 17 May 1993 10:51:12 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: ACCESS REPORTED BUGS!
In-Reply-To:  Message of Mon,
              17 May 1993 23:39:32 EST from <[e-mail] NASH.EDU.AU>

That file is available from LISTSERV@INDYCMS as ACCBUG TEXT.

Nathan Brindle
ACCESS-L List Administrator

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Mon, 17 May 1993 08:54:22 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Making fields shrink on reports

I'm having trouble getting some text controls on a report to shrink.
In dealing with addresses, I have fields defined as "Address1",
"Address2", "Address3", "City", "State", "Zip", etc. Sometimes, there
is not any data in Address3. So, I want City, State and Zip to move up
on the report so there won't be a blank line.

There's a control property called "shrink" (at least I think that is the
name. I don't have access running here). If set to "yes", it should do what
I am asking. It seems to work fine on some reports. Others, it does not
shrink the blank lines.

How do you handle this?


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Mon, 17 May 1993 10:19:11 MDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     Converted from PROFS to RFC822 format by PUMP V2.1
From:         Jack Wiercinski <[e-mail]>
Subject:      Help! Access add tables to my database!
In-Reply-To:  note of 93-05-17 00:56

All six tables with names MS* are system tables. Don't try to
delete them. Use VIEW -> OPTION... -> SHOW SYSTEM OBJECT -> NO to hide
them. You may wish to look into these tables in a datasheet view as an
interesting exercise.
Good Luck, ("Powodzenia")

Jack                                    ISD NAIT [phone]
=========================================================================
Date:         Mon, 17 May 1993 13:37:00 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Mon, 17 May 1993 13:37:00 EST
=========================================================================
Date:         Mon, 17 May 1993 13:38:03 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Mon, 17 May 1993 13:38:03 EST
=========================================================================
Date:         Mon, 17 May 1993 13:38:22 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Mon, 17 May 1993 13:38:22 EST
=========================================================================
Date:         Mon, 17 May 1993 13:38:04 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Mon, 17 May 1993 13:38:04 EST
=========================================================================
Date:         Mon, 17 May 1993 13:38:23 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Mon, 17 May 1993 13:38:23 EST
=========================================================================
Date:         Mon, 17 May 1993 15:38:30 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Greg Fairnak <[e-mail]>
Organization: The American University
Subject:      dos 6.0, stacker. et al

Be careful when using a stacker type software with permanent Windows swap
files.  Swap files do not like to be placed on stacked drives.  I am
running dos 6.0 with compression and have had no problems.  I stacked entire
drive, killed my permanent swap file and replaced it with a temporary swap
file.  The temp swap file gets along with dos 6.0 dblspace.  Now for one of
my problems:  Wrote a few big queries and I get out of memory errors.  I have
checked the MSDEV CD-ROM and found some hints.  Could some one chime in with
a complete list of out of memory work arounds?  I saw increasing files= a few
days ago.  Has someone written an error handler to crash gracefully in this
case?

Thanks in advance,
                  G
=========================================================================
Date:         Mon, 17 May 1993 16:08:34 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> E: "From:"/"Sender:" field is missing.
From:         Undetermined origin c/o Postmaster <[e-mail]>
Subject:      Service Message

Content-type: REPORT

Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
Reason: Failed to transfer; communications failure (0)
Arrival-date: Mon, 17 May 1993 16:08:34 EST
=========================================================================
Date:         Mon, 17 May 1993 14:14:27 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Hal Stitt <[e-mail]>
Subject:      Re: Service Message

I,m still getting this report. It's up to about 20 times by now. Can you do
anything to stop it?
Hal Stitt
=========================================================================
Date:         Mon, 17 May 1993 16:01:14 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         John von Colditz <[e-mail]>
Subject:      Re: file sizes
In-Reply-To:  <[e-mail]> from "JULIAN BOOT,
              UNIVERSITY BOOKSHOP" at May 17, 93 10:57:14 pm

>
> I have been reading with some interest the tales of woe relating to
> data compression software and the aparent stability of MS's new product
> bundled with DOS 6.
>
> I have had in the past problems with SuperStor and DoubleDensity (from Abacus)
> and looked at Stacker before deciding to purchase a second hard disk.
 Problems
> usally resticted themselves to programs not running or false "fatal error"
> reports - occasionally I would lose the odd file, but this happens with a
 non-c
> compressed FAT disk anyway.
>
> My question is this.  Does anybody actually *know* what Access is doing to
>  causethese problems?  One possible answer I have heard is MS programmers have
>  been
> using some tricks Stacker does not know about in an attempt to get people
> who need datacompression, but not a new DOS, to upgrade anyway.  This does
 seem
> a tad scynical, however.
>
> Julian Boot
> Computer Science
> University of Queensland
> Brisbane, Australia
> Internet:  [e-mail]
>

Julian,

There is an interesting article in InfoWorld this week by Steve Gibson.
It appears that the problem is not with the disk compression software,
but with smartdrive.  Smartdrive does lazy writes, which means it waits
until nothing is going on until it writes data.  There is a whole class
of users out there who have been trained to exit their word processor,
exit windows and turn their machine off.  Smartdrive may not have
written the final save, and the file gets trashed.  Gibson has written a
TSR that forces smartdrive to write to disk before exiting windows.  It
is on the Gibson Research BBS, and on CompuServe.  Steve can be reached
on Internet at [e-mail].

Hope this helps.

John
=========================================================================
Date:         Mon, 17 May 1993 16:03:30 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         John von Colditz <[e-mail]>
Subject:      Re: dos 6.0, stacker. et al
In-Reply-To:  <[e-mail]> from "Greg Fairnak" at May 17,
              93 03:38:30 pm

Just a note: NEVER, NEVER, EVER PUT A WINDOWS SWAP FILE ON A STACKED
DRIVE.  YOU WILL PAY!!!!

thank you.
=========================================================================
Date:         Tue, 18 May 1993 09:07:09 -0500
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         elizabeth klaver <[e-mail]>
Subject:      Re: Disk Compression, Access, Smart(?)Drive

My system is a 386DX, 6M ram, running DRDOS 6, with 2 Superstor'd drives,
and QEMM. I run Windows (and Access) both stand-alone and within a DESQview
window. Yet, until Saturday last I had experienced none of GP faults or
disk crashes that have been mentioned in this list. Out of curiosity I
ran Smartdrive to see if it would make any appreciable difference in
the performance of Access. Before Access could finish its first 'Select'
I had one GP fault, when I restarted Access I immediately got a Page Fault.
When I tried to reboot after removing smartdrive I found one of my disks
to have been trashed.
Can any one else trace these problems so directly to smartdrive?
Thanks ET Klaver
=========================================================================
Date:         Tue, 18 May 1993 14:05:15 +0200
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Gernot Starke <[e-mail]>
Subject:      Unsubscribe

Please remove me from the ACCESS-L list.

[e-mail]
=========================================================================
Date:         Tue, 18 May 1993 09:04:41 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Service Message
In-Reply-To:  Message of Mon,
              17 May 1993 14:14:27 -0700 from <halstitt@NETCOM.C OM>

On the "Service Reports":  I have deleted the subscriber from the list
(did that Sunday, in fact!) and have sent a letter to the postmaster at
the named site.  Since the messages don't come with a "From:" or "Sender:"
field, I have no other options.

All I can say is, I'm trying to get them stopped.

Nathan Brindle
ACCESS-L List Administrator

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Tue, 18 May 1993 08:12:03 MDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     Converted from PROFS to RFC822 format by PUMP V2.1
From:         "Brian Keeler (403) - 471-8623" <[e-mail]>
Subject:      Making fields shrink on reports
In-Reply-To:  note of 93-05-17 10:56

I had the same problem, what I did in the report design was have 2 statements
for the address, if address1 was there it printed and if address2 it printed
after it, if addr1 was blank it moved it up a line. Do the following:

addr1 =iif(([addr2]is null),"|[city]|, |[prov]|, |[pcode]|","|[addr2]|")
addr2 =iif(([addr2]is null),"|[addr2]|","|[city]|,b|[prov]| |[pcode]|")

Ensure that your square brackets, quotes and straightline/bar key characters
all match. Anyway if the 2 address lines are present they print, if the second
one is blank, everything moves up one line.
Have a good day..ps watch that you do not make the field eg. field84 the same
as the your data name, you will have nothing but problems and things like the
formula above will not work.....

Brian Keeler (403) - 471-8623     ..What is a CD-ROM ??
Application Services Coordinator   3 billion pits arranged
Information Services Division      in a 3 mile spiral...
domain: [e-mail]
=========================================================================
Date:         Tue, 18 May 1993 07:51:44 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Re: Disk Compression, Access, Smart(?)Drive

>
> My system is a 386DX, 6M ram, running DRDOS 6, with 2 Superstor'd drives,
> and QEMM. I run Windows (and Access) both stand-alone and within a DESQview
> window. Yet, until Saturday last I had experienced none of GP faults or
> disk crashes that have been mentioned in this list. Out of curiosity I
> ran Smartdrive to see if it would make any appreciable difference in
> the performance of Access. Before Access could finish its first 'Select'
> I had one GP fault, when I restarted Access I immediately got a Page Fault.
> When I tried to reboot after removing smartdrive I found one of my disks
> to have been trashed.
> Can any one else trace these problems so directly to smartdrive?
> Thanks ET Klaver
>

I have just about given up on using disk compression under DOS. It seems that
there are just too many ways that programs can unintentionally cause havoc to
the system. I used to use Superstore and also had problems like yours (except
I was not using Access at the time). I ended up just buying a larger drive.
I will probably re-examine disk compression again after it is part of NT or
 OS/2.

BTW, unless you live on the edge, make sure that smartdrive has disabled the
write cache. By default (through setup) it is enabled. With smartdrv, the write
cache will not flush all contents to disk unless you manually flush the cache.
This means you cannot reboot or power off your machine without flushing the
 cache.
Peronally, I can't live with the write cache because Windows does not do a good
enough job of protecting you from misguided software (including my own).
I would rather just get the benefit of caching the read requests for now.


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Tue, 18 May 1993 09:31:46 -0600
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Thomas D. Gasser" <[e-mail]>
Subject:      Re: Service Message

In message Mon, 17 May 1993 16:08:34 EST,
  Undetermined origin c/o Postmaster <[e-mail]>  writes:

>Content-type: REPORT
>
>Report on your message to: /R=AM/U=NGUYEN/@MASTER.NIMH.NIH.GOV
>Reason: Failed to transfer; communications failure (0)
>Arrival-date: Mon, 17 May 1993 16:08:34 EST


    *********************************************************************
    *  Thomas D. Gasser                                                 *
    *  Department of Neurosurgery                *******     ******     *
    *  University of Minnesota                    ***  *** *** ***      *
    *  [phone]                             ***   *****  ***      *
    *  E-Mail:  [e-mail]         *****        *****     *
    *                                                                   *
    *********************************************************************
=========================================================================
Date:         Tue, 18 May 1993 10:21:25 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         John von Colditz <[e-mail]>
Subject:      Access 1.1 Upgrade
In-Reply-To:  <[e-mail]> from "Jim Renaud" at May 17,
              93 08:54:22 am

Ladies and Gentlemen,

Although the product has not been officially announced, Microsoft (at
least through Developer Support) is taking orders for Access 1.1!
$14.95 + $5.00 S/H.

Thought you might like to know.

John
=========================================================================
Date:         Tue, 18 May 1993 22:23:47 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         [e-mail]
Organization: Willard's House BBS, Atlanta, GA -- [phone]
Subject:      broken mail through my site

My humblest apologies to the members of this mailing list for the
recent screwup that resulted in several bounce messages being
propagated back to the mailing list.  The explanation is simple,
though perhaps that does not really matter to you.  I just did an OS
upgrade on hobbes, from SunOS 4.1.1 to Solaris 2.1, and in so doing,
happened to break mail to a couple of users, one of which is receiving
the Access mailing list from my site here at willard.atl.ga.us.  The
problem has been resolved, and you should not see further occurrences
off this error message from this side of the world.  Thank you for
your patience.

--
[e-mail] (Willard Dawson)
gatech!kd4nc!vdbsan!willard!dawson
emory!uumind!willard!dawson
Willard's House BBS, Atlanta, GA -- [phone]
=========================================================================
Date:         Wed, 19 May 1993 08:57:55 EST
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Pekka Koskinen <[e-mail]>
Subject:      Re: file sizes

On Mon, 17 May 1993 16:01:14 -0700, John von Colditz wrote:

>
>There is an interesting article in InfoWorld this week by Steve Gibson.
>It appears that the problem is not with the disk compression software,
>but with smartdrive.  Smartdrive does lazy writes, which means it waits
>until nothing is going on until it writes data.  There is a whole class
>of users out there who have been trained to exit their word processor,
>exit windows and turn their machine off.  Smartdrive may not have
>written the final save, and the file gets trashed.  Gibson has written a
>TSR that forces smartdrive to write to disk before exiting windows.  It
>is on the Gibson Research BBS, and on CompuServe.  Steve can be reached
>on Internet at [e-mail].
>
>Hope this helps.
>
>John

The explanation makes sense to me. What I have done is to use the
command "smartdrv /c"; I thought that it does the same thing. So I have
a following bat-file to start windows:

             WIN :
             SMARTDRV /C

I have understood that this makes sure that you don't get the C> -prompt
until smartdrv has finished it's job. Isn't this enough?

Pekka

:) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :)

    _/_/_/_/   _/   _/_/  _/_/  _/_/_/_/
   _/    _/   _/   _/ _/_/ _/  _/    _/  "Taste is the fundamental quality
  _/         _/   _/      _/  _/    _/   which sums up all other qualities"
 _/    _/   _/   _/      _/  _/    _/
_/_/_/_/   _/   _/      _/  _/_/_/_/            (C. de Lautveamout)

Pekka Koskinen    tel [phone]    fax [phone]
CIMO, P.O. Box 343, 00531 Helsinki, FINLAND
=========================================================================
Date:         Thu, 20 May 1993 07:41:24 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Access Listserv <[e-mail]>
Subject:      Visual Basic 3.0 Professional versus Access 1.1

FYI:

    After reading some interesting information/rumors on the upcoming
releases of both Visual Basic Pro 3.0 and Access 1.1, I called the
Microsoft Developer Network yesterday to get the skinny and place an order
or two.  Here is what I found out:


Visual Basic 3.0 Professional

Released next week
$99 upgrade from 2.0 Pro, $149 upgrade from 2.0, $395 intro price, $495 list
Contains Access 1.1 Database engine
Most controls have now been modified to be 'data aware'
    (i.e. they can be attached to table fields)
Uses Crystal Reports 2.0 for its reporting
    The rep said that it is very similar in function to the reports in Access
Can create a standalone executable with database extensions
It cannot:
    use Access Macros
    use Access Queries
    use Access Reports (Crystal Reports instead)


Access 1.1

Released in 4-6 weeks
$15 upgrade from 1.0
Does not include database compiler


So, I told the lady that I'd like to order VBPro 3.0 now and hold off on
Access 1.1 upgrade.  I figure 3-5 weeks is plenty of time to figure out if
VBPro can replace Access for most uses (and figure out just how
detrimental the lack of queries is going to be).  I'll try it out and
report back here what I find.

 - jcb
=========================================================================
Date:         Thu, 20 May 1993 11:09:37 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Jim Renaud <[e-mail]>
Subject:      Re: Visual Basic 3.0 Professional versus Access 1.1

> It cannot:
>     use Access Macros
>     use Access Queries
>     use Access Reports (Crystal Reports instead)

I went to the Microsoft DEVCAST last week and a Microsoft employee indicated
that Tables and Queries would be accessible from the Access 1.1 engine. I will
have to lookover the foils to see if this was indeed true.

Either way, the VB3.0 announcement (w/Access 1.1 engine) tells me that Microsoft
is commited to support Access in the future. Also, they indicated that they
expect people to do development in VB3.0 (forms and code) instead of using
the equivalent in Access. VB3.0 supports add-on controls and is very extensible.
I will probably use VB3.0 for the front end since it is more flexible.
Also, you can use revision control software with VB, not with Access.

I also thought it was interesting that Microsoft did not mention FoxBase in
any discussions about database technology. I was disappointed to learn that
 there
is currently no plans to implement the Access 1.1 engine into Visual C++.


-----------------------------------------------------------------------

Jim Renaud                              [Standard Disclaimer]

Amdahl Corporation
M/S 205                                 Phone:  [phone]
Bldg. M3  Room 235                      Fax:    [phone]
1230 E. Arques Avenue                   Email:  [e-mail]
Sunnyvale, CA 94088-3470
=========================================================================
Date:         Thu, 20 May 1993 15:52:09 CDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         James Ford <[e-mail]>
Subject:      3090 DB2 Database to Novell possible?

Is there any way to set up some sort of database on a Novell server
which could access a DB2 database on an IBM3090 with SQL (or something)?
What I would like to do is have a PC/Mac client request info from a
Novell-based process which would then query our mainframe's database.
We use both SNA and TCPIP for accessing the 3090, though the DB2 info
has to go through the SNA net.


Client request----------> Novell NLM  -----------> IBM3090 DB2 database
                         database engine?

What other ways could one use to get DB2 info to a client?  This does
not have to include Novell......

Please reply directly to [e-mail].  Thanks in advance.....
----------
Budget: an orderly system of living beyond your means.
----------
James Ford -  Consultant II, Seebeck Computer Center
              The University of Alabama (in Tuscaloosa, Alabama)
              [e-mail], [e-mail]
              Work [phone]  fax [phone]
=========================================================================
Date:         Thu, 20 May 1993 19:07:09 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Greg Fairnak <[e-mail]>
Organization: The American University
Subject:      Help with passing a string to SQL

Hello everyone,
     I need a hand from somebody.  I have a combo box on the screen
titled MyName.  The combo box has a field list with "STEVE" selected.
From a the on Push properties of a button I call =GetMyQuery(MyName).
How do I pipe MyName into the Where properties of a PARAMETER Query.
Such as:

  Function GetMyQuery(MyName as String)
       Dim SQL
       SQL="Select * from table Where table.name = [MyName]";

  End Function

I make a dynaset and then ddepoke the values to excel.  If I hardcode
a value the query and dynaset work fine.  If I try an pass it a string
no luck? :-(  Could someone toss a little bit of sample code up on the
list to help me.
                 Thanks, :-)
                        Greg
=========================================================================
Date:         Fri, 21 May 1993 09:01:54 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Greg Fairnak <[e-mail]>
Organization: The American University
Subject:      Passing strings to a querydef

Does anyone know how to properly format a QuerfDef using parameter variables
of the type string?

E.G.  SQL="Parameters NAME as String; Select * from table where table.name=
           NAME;"

I think the problem has to do with the formatting of the search quotes.


Thanks,
       G
=========================================================================
Date:         Fri, 21 May 1993 09:48:53 CST
Reply-To:     [e-mail]
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "John A. Olson" <[e-mail]>
Subject:      Re: Help with passing a string

what you need to do is this:

In your function,
Function GetMyQuery(MyName as String)
       Dim SQL
       SQL="Select * from table Where table.name = [MyName]";

where it says [MyName] it should be written as:

       SQL="Select * from table Where table.name = [" & MyName & "];"

This should take care of your problem.

Good Luck!

John A. Olson
[e-mail]
John A. Olson
Internet address:  [e-mail]
=========================================================================
Date:         Fri, 21 May 1993 19:20:33 BST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Anne L Zorner R27.G5/" <[e-mail]>
Subject:      re security

SQL Support Section (SQS)         Mail [e-mail]
===============================================================
Following the attendance of an excellent course on ACCESS given by
Microsft earlier this week, a number of things have become clearer.
The main one is that Access can indeed be made secure. It just needs
a little more effort than it at first appears in the manuals.
They gave us a check list which I have added here.
1 Create a secure workgroup & use it
2 add a developer account to the workgroup
3 exit and restart access
4 log on to the developer account
5 create a NEW database so that it will be owned by the newly
created developer account (userid)
6 create the protected objects, or copy and paste them from the old
database (could use import)
7 remove permissions for the protected objects making sure to remove
all permissions from USERS, GUESTS and ADMINS, note this is especially
the case if you use IMPORT.
8 assign permissions as you want them. remember dont deassign permissions
from yourself, if no one else has them then you will not be able to get
them back!

To create the secure workgroup as defined in 1 basically follow
the process in the manuals.

You may want to think about who is going to administer the system
because you cant leave the ADMINS group with any permissions.
If you do then remote ADMIN account could use the data. So basically
it looks like you have to get everyone to assign permissions to a new
group of administrators if you want them to be able to administrate
your tables for you.
I am not totally sure what it means if you do not allow the administrator
to administrate your tables. I have the feeling that it could mean
that they are not able to delete tables that you own, should you
leave the comapny taking your password with you.

Careful control may need to be made in the administration of these
databases as it looks like you may not be able to stop people
creating tables in your database if they have write access to the
file or directory.

One suggestion that Microsoft made at that seminar was to
have the data in a separate database to the queries etc and
just use attach to get the to your database where you put the queries
forms etc. This seems like a good idea. The question is if you can
attach to a database then presumably you can use it directly? at
least to the point where you the user could store your own tables
in it, this might not be desirable from the data storage capacity
point of view. I wonder whether it can be avoided?
Anne

Thankyou
===============================================================
=========================================================================
Date:         Fri, 21 May 1993 12:53:27 PDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         RAM DIMBA <[e-mail]>

I have uploaded the following files at ftp.cica.indiana.edu
These files were downloaded from COMPUSERVE.

 :accpac.txt
:ACCPAC.ZIP
:accpan.txt
:ACCPAN.ZIP
:accut.txt
:ACCUT.ZIP
:chgprn.txt
:CHGPRN.ZIP
:CHKPRT.ZIP I am sorry I did not upload this.. next time
:contin.txt
:CONTIN.ZIP
:dbtips.txt
:DBTIPS.ZIP
:fifo.txt
:FIFO.ZIP
:galxy2.txt
:GALXY2.ZIP
:grpins.txt
:GRPINS.ZIP

Most of the above files were interesting and informational.

There are more files on Compuserve!!  Because of the expense, I
had to cancel my membership!!  Could any of the Compuserve users
kindly upload files on CICA?

Thanks

Ram Dimba
=========================================================================
Date:         Fri, 21 May 1993 16:24:00 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Trufant, Jamie" <[e-mail]>
Subject:      Foxpro list server

Does anyone out there know of a Listserver for FoxPro users?  I use both
Access and FoxPro. I find this list helpful with Access.  It would be nice
to also be on a list for FoxPro.

Thanks for any information you can give me.

 -- Jamie Watts

    Registrar's Office
    Ohio State University
    Columbus, Ohio
=========================================================================
Date:         Fri, 21 May 1993 15:31:11 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Re: Foxpro list server
In-Reply-To:  Message of Fri,
              21 May 1993 16:24:00 EDT from <[e-mail]. OHIO-STATE.EDU>

LISTSERV LISTS (a file which you can have sent to you by sending any
LISTSERV the command LIST GLOBAL--but warning, it's 3000+ lines long)
does not show any list for FoxPro unless I just plain missed it.  There
is no FOXPRO-L, at any rate.

I'd start one for you, but I have my hands full as it is...:)

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Mon, 24 May 1993 13:54:00 GMT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     <Parser> W: Invalid RFC822 field - "EA - Science Park))". Rest of
              header flushed.
From:         [e-mail]

Please remove me from the ACCESS-L list

[e-mail]
=========================================================================
Date:         Mon, 24 May 1993 09:05:20 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
In-Reply-To:  Message of Mon,
              24 May 1993 13:54:00 GMT from <[e-mail] ESTE.IT>

Your request for removal from the ACCESS-L list at INDYCMS has been
received.

Unfortunately, I am unable to remove you from the list because LISTSERV
reports that you are not found in the list.  You may be subscribed via
a mail redistribution network.  If this is so, I have no control and
you will have to contact the operator of the redistribution account
to remove you from the list.

Nathan Brindle
List Administrator, ACCESS-L@INDYCMS

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Mon, 24 May 1993 09:16:48 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Oops

Sorry about that last post.  It was supposed to go to one person.

Mondays....

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Mon, 24 May 1993 11:42:18 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Joe Svitak <[e-mail]>
In-Reply-To:  Message of Mon,
              24 May 1993 13:54:00 GMT from <[e-mail]>

Send an E-mail message to [e-mail] with the following
line:

signoff access-l
=========================================================================
Date:         Mon, 24 May 1993 15:59:13 EDT
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Greg Fairnak <[e-mail]>
Organization: The American University
Subject:      parameter queries

Has anyone had any success with using parameter queries with a String variable?
If you have,please post an example onto the list.  I seem to be having a very
difficult time.  I keep on getting invalid parameters clause error message.

Thanks for the help,


 Virtually Yours,
                 Greg
=========================================================================
Date:         Mon, 24 May 1993 13:47:48 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         John von Colditz <[e-mail]>
Subject:      Re: parameter queries
In-Reply-To:  <[e-mail]> from "Greg Fairnak" at May 24,
              93 03:59:13 pm

>
> Has anyone had any success with using parameter queries with a String
 variable?
> If you have,please post an example onto the list.  I seem to be having a very
> difficult time.  I keep on getting invalid parameters clause error message.
>
> Thanks for the help,
>
>
>  Virtually Yours,
>                  Greg
>

Greg,


1)  Build your query with the query builder, with a criteria for the
field you want to substitute for (=Jones in the Name field).  Make sure
the query runs correctly.

2)  From the query screen, go to View SQL.  Highlight the SQL, and use
^C to copy it to the clipboard.

3)  Go into the module that will do the query.  Use ^V to paste the SQL
in.  You will have to get out the CRLF combinations, and make it a
string.

4)  Where your criteria is in your query, you will find something like =
"Jones".  Do the following:  a) To the left of the first quote, place a
single quote (').  b)  Add an & on each side of Jones.  c)  Replace
Jones with the variable you wish to paste in.  You end up with something
like:
SQL =  "        SELECT * FROM PEOPLE WHERE PEOPLE.[NAME] = '" & YourVar & "'blah
You now have a varible named SQL with you query in it, and your variable
in the where clause.

5)  Now use either DoCmd RunSQL SQL or use the Create/Modify Querydef
methods.  RunSQL will only work if SQL is < 256 characters long.  You
can't run things like delete queries using QueryDef's (I don't think),
so there are some limitations on your activities.

Good luck.

John
=========================================================================
Date:         Wed, 26 May 1993 16:07:57 +0200
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Rory Browne <[e-mail]>
Subject:      Cusomized Menu Bar

How do I create an entry on my drop-down list similar to the one used on
the FILE/NEW-> list?. I need to be able to create a list of choices which
the user may select in a similar fashion the functionality of this option.


Regards
=========================================================================
Date:         Wed, 26 May 1993 07:24:01 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Bill Stewart <[e-mail]>
Subject:      Re: Cusomized Menu Bar

It sounds like maybe an API to bring up a dialog box would work, or
possibly building a form to hold the information you want to prompt the
user with.

_________________________________________
Glendale Community College - Bill Stewart
6000 W. Olive Ave.
Glendale, Az. 85302
[phone]
_________________________________________
=========================================================================
Date:         Thu, 27 May 1993 10:46:10 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Help with a unique query

Help meeeee....either I'm missing something or it just won't do this.

I have a table with fields FirstName, LastName, Organization, Address, etc.
There are a number of records that have the same FirstName and LastName
but the Organization is unique in each case, Address etc. may or may not
be different (depending on who input the record...it may be First Street or
1st St. or some other permutation).

What I need to do is print mailing labels for unique values of FirstName and
LastName (whether or not every Organization gets printed is not important)
but I still need to print Organization, Address, etc. on the labels.  Setting
the Unique Values box in Query Design doesn't work unless I leave Organization
out.  I tried messing with the SQL statement but don't have the knowledge to
change it correctly.

I used to do this in dBase routinely...can anyone shed some light?  TIA,
-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] (preferred) or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Thu, 27 May 1993 10:58:56 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      one more piece of info

In refererence to my last post, what I want to do is done in dBase IV by
creating an index and setting "Display 1st Duplicate Record Only" to Yes
in the index dialog box.

Thought I ought to clarify that.

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] (preferred) or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Thu, 27 May 1993 12:12:08 EST
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Nathan Brindle <[e-mail]>
Organization: IUPUI Student Activities Office [phone]
Subject:      Help no longer needed:)

I found it, I found it...but not in the manual.  Geez....

I had to set up a summary query (I think that's what it's called--anyway,
you do it by hitting the sigma button at the top) and set LastName and
FirstName to Group By and all the other fields to First.  This is NOT
well documented, Microsoft.....

If anyone is out there frantically looking, you can stop now.  Thanks!

-----------------------------------------------------BITNET:  NBRINDLE@INDYCMS
Nathan C. Brindle, Administrative Specialist, Student Activities Office
Indiana University Purdue University Indianapolis
Staff Advisor, ALPHA PHI OMEGA, TAU OMICRON CHAPTER
List Administrator, STUACTS@INDYCMS, APOSEC52@INDYCMS, and ACCESS-L@INDYCMS
Internet:    [e-mail] (preferred) or [e-mail]
------------------------------------------------------------------------------
=========================================================================
Date:         Thu, 27 May 1993 12:48:41 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
Comments:     Warning -- original Sender: tag was
              [e-mail]
From:         "Linda D. Cornell" <[e-mail]>
Subject:      Need help understanding Access key structure
In-Reply-To:  <[e-mail]>

Hi there,
I'm using Access to build a prototype of a fairly large complex database,
and I am running into difficulties understanding how it handles keys.

In design mode, you can set a key for any row in the definition table -
great, just point and click.  This automatically sets the indexing as No
Dups - great.

I this design lends itself to concatenated keys, so an intermediate table
might have 4 rows in the definition table designated as keys.

However, when you try to designate a relationship between a table with a
"4-plex" key structure (primary table) and another (secondary) table,
Access tries to force you to use all four parts of the key structure.  It
won't let you use just the one part of the key applicable to the link.

I can nuke the keys and just play with combinations of indices that will
mimic a concatenated key structure - but I feel like I must be missing
something.

Any comments about keys?....and....other than deleting a row that has been
designated as a key, and re-entering it as a non-key, is there any way to
remove the key designation?

All answers are welcome!  My thanks are in advance!

Linda Cornell
[e-mail]
UW Office of Research
=========================================================================
Date:         Thu, 27 May 1993 13:58:36 -0700
Reply-To:     Microsoft Access Database Discussion List
              <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         Brian Henning <[e-mail]>
Subject:      Re: Need help understanding Access key structure

>However, when you try to designate a relationship between a table with a
>"4-plex" key structure (primary table) and another (secondary) table,
>Access tries to force you to use all four parts of the key structure.  It
>won't let you use just the one part of the key applicable to the link.

If I'm reading your question correctly the table with the 4 keys will be
referenced from another table with a foreign key. In that case you must use all
4 attributes, that's the way foreign keys work. Anything less would result in a
non-unique reference to the primary table.

Example

Table - A
Parts List
Primary key - Mfg, Model #

Table - B
Order
Primary key - Invoice #
Foreign key - Mfg, Model #

If I want referential integrity between these two tables then I must use the
whole primary key of A. If I have some table C that I want to tie to say Mfg
alone then I must have a seperate table in which Mfg is the sole attribute in
the primary key.

I'm sure someone else can do a better job explaining this then me.

Brian Henning
[e-mail]
=========================================================================
Date:         Fri, 28 May 1993 13:03:03 -0700
Reply-To:     "Linda D. Cornell" <[e-mail]>
Sender:       Microsoft Access Database Discussion List
              <[e-mail]>
From:         "Linda D. Cornell" <[e-mail]>
Subject:      Re: Need help understanding Access key structure
In-Reply-To:  <[e-mail]>

> However, I have not tried to relate multiple
> primary records to a single child record ... is this what you're trying to
> do?

Nope, I'm still trying to do a one to many.

I started writing this horrendously long e-mail response with one of my
examples, but it was getting too lengthy and didn't get to the point that:

1)  I always understood that a relation could exist between 2 tables as
long as there was a common field to link the tables and that the relation
was at most a "one-to-many".  Key structures ensure the integrity of a
specific table - but now I'm starting to see that using the full
concatenated key enforces the "one" part of the "one-to-many" - in an
effort to "simplify" apparently I was "cutting corners" inappropriately
and Access didn't like that ;)!

2)  However, in Access, what is the difference between an "Index with no dups"
and a "key"? - other than the software does comparisions and error checking
using this "key" as an attribute.  It seems to me that both the "no dup
index" and the "key" should yield the same physical result in a table.

3)  and if you use a concatenated key, there is no way to index the whole
key, you can only do an index with dups on a partial key.  This can be
worked around for smaller tables, but it really could get ugly in larger
tables!

Anyway, just food for thought!

Linda
[e-mail]
University of Washington
Office of Research